|Policy Name||Availability Group Online State|
|Issue||Availability group is offline.|
This policy checks the online or offline state of the availability group. The policy is in an unhealthy state and an alert is raised when the cluster resource of the availability group is offline or the availability group does not have a primary replica.
The policy state is healthy when the cluster resource of the availability group is online and the availability group has a primary replica.
For this release of SQL Server 2017, information about possible causes and solutions is located at Availability group is offline on the TechNet Wiki.
This issue can be caused by a failure in the server instance that hosts the primary replica or by the Windows Server Failover Cluster (WSFC) availability group resource going offline. Following are possible causes for the availability group to be offline:
The availability group is not configured with automatic failover mode. The primary replica becomes unavailable and the role of all replicas in the availability group become RESOLVING.
The primary replica instance service is down or unresponsive.
The availability group has a connectivity issue with the cluster.
The availability group is configured with automatic failover mode and does not complete successfully.
- During the automatic failover, the primary readiness check on the target replica fails, and there is no replica available to become the new primary.
The availability group resource in the cluster becomes offline.
Any dependent cluster resource encounters a critical issue and becomes offline. The availability group resource is also offline until the dependent resource becomes online.
A critical issue in the cluster turns off the availability group resource.
There is an automatic, manual, or forced failover in progress for the availability group.
Following are possible solutions for this issue:
If the SQL Server instance of the primary replica is down, restart the server and then verify that the availability group recovers to a healthy state.
If the automatic failover appears to have failed, verify that the databases on the replica are synchronized with the previously known primary replica, and then failover to the primary replica. If the databases are not synchronized, select a replica with a minimum loss of data, and then recover to failover mode.
If the resource in the cluster is offline while the instances of SQL Server appear to be healthy, use Failover Cluster Manager to check the cluster health or other cluster issues on the server. You can also use the Failover Cluster Manager to attempt to turn the availability group resource online.
If there is a failover in progress, wait for the failover to complete.