Hello,
I have created a SQL Server 2012 Always on Availability Group with 2 nodes. I can failover manually.
in the properties of the AG I can see that the Availability Mode is Synchronous Commit and the Failover Mode is automatic.
If I right click on the AG and click failover, I can successfully do failover.
In my Cluster Manager I have configured the quorum setting to include the 2 servers as well as 1 file share (which is accessible and up and running).
Now if I stop the SQL Service instance on one of the machines. I can see that the AG on the 2nd machine goes into "resolving" state... but it never comes out.
in the FC Manager I can see the errors like
Clustered role 'SP2013SQLAG' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
- The Cluster service failed to bring clustered service or application 'SP2013SQLAG' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
- Cluster resource 'SP2013SQLAG' of type 'SQL Server Availability Group' in clustered role 'SP2013SQLAG' failed.
- Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
What is causing the automatic failover to error out when manual failover is working fine?
val it: unit=()