Hi All
We have a SQL Always on availability group consisting of 2 nodes 'Node A' and 'Node B'. We have configured the patching reboot windows for these servers in such a way that 'Node A' always reboots first, followed by 'Node B' approx. 2 hours later. This should ensure that our SQL AG always ends up running in 'Node A' post patching.
However, we have recently had an issue where the AG ends up running in 'Node B' despite Node B rebooting last (hence the AG should fail back over to Node A?). I ran a Powershell query to retrieve the failover history and notice the following:
At 02:40 (When Node A was rebooted)
26/01/2020 02:40:08 1641 Information Clustered role 'Client_AG' is moving from cluster node 'Node A' to cluster node 'Node B'.
At 04:46 (when Node B was rebooted) the Client_AG didn’t move back to A as expected:
26/01/2020 04:46:34 1641 Information Clustered role 'Client_AG' is moving from cluster node 'Node B' to cluster node 'Node B'.
Does anyone know why the AG failved over from 'Node B' to 'Node B' ?! This doesn't make any sense to me.
Thanks in advance for any answers.
Regards,
Phil