Forum Discussion
Availability Group failover issue
AG is quite reliable but this king of things may happen. Is there any error log that could point out of why there was a failback from B to A and it did not started.
My suggestion will be to take a maintenance Window and try to switch roles to all nodes. Also run the cluster verification process to see if you get any warning from there
I think the failback from B to A occurred because the AG failed to come up on B. At the time we were using the default value for the "maximum failures in the specified period" setting in Failover Cluster Manager. We have since increased that from 2 to 6 in the hope that a future failure will make additional attempts to bring the AG online on the failover partner.
We have also manually failed over the AG between all three nodes without issue. The Cluster Validation Report shows all tests are passed.