问题描述
我们每月在运行sql server 2008 r2和sql server 2012的Windows 2008群集上运行windowsupdate。这将进行修补，然后重新启动服务器，默认情况下所有实例都将在一个节点上运行，以先到者为准。我们为每个组配置了
autofailback，这样6个实例将出现在他们的"首选"节点上以优化性能。我们只在windowsupdate运行的日期/时间启用autofailback，然后再次禁用它，因为我们不希望它在正常的
操作期间启动。
Each month we run windowsupdate on a windows 2008 cluster running sql server 2008 r2 and sql server 2012. This will do the patching and then reboot the servers, and by default all the instances will end up on one node, whichever came up first. We have configured autofailback for each group, so that the 6 instances will come up on their 'preferred' node to optimise performance. We enable autofailback only during the date/time that windowsupdate will run, then disable it again as we don't want it to kick in during normal operation.
上个月这个进程失败，所有实例都出现在1个节点上。唯一明显的区别是（备份）服务无法启动。这种情况在4个集群上以类似的方式发生。
Last month this process failed and all the instances came up on 1 node. The only obvious difference being that a (backup) service failed to start. This happened in a similar way on 4 clusters.
是autofailback无法发挥其魔力的原因，因为如果服务所在的组不来，它就不会启动"失败"或可能"失败"状态？
is the reason that autofailback failed to do its magic because it doesn't kick in if the group doesn't come if a service is in a 'failed' or possibly 'failing' state?
推荐答案
这篇关于sql server 2008 - 故障恢复无法按预期工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！