This monitor checks the online or offline state of availability group. The monitor is in unhealthy state and alert is raised when the availability group’s cluster resource is offline or the availability group does not have a primary replica. The monitor state is healthy when the cluster resource of availability group is online and the availability group has a primary replica. This monitor is a dependency (rollup) monitor.
Knowledge Base article:
Summary
This monitor checks the online or offline state of availability group. The monitor is unhealthy and alert is raised when the availability group’s cluster resource is offline or the availability group does not have a primary replica. The monitor state is healthy when the cluster resource of availability group is online and the availability group has a primary replica.
Causes
The availability group is offline, and is unavailable. This issue can be caused by a failure in the server instance that hosts the primary replica or by the WSFC availability group resource going offline.
The availability group is not configured with the automatic failover mode and the primary replica become unavailable and the role of all replicas in the availability group become RESOLVING.
Primary replica instance service is down or unresponsive.
The availability group has a connectivity issue with the cluster.
The availability group is configured with the automatic failover mode and the automatic failover is not completed successfully due to error.
During the automatic failover, the primary readiness check on the target replica fails and there is no replica to become a new primary.
The availability group resource in the cluster becomes offline.
Any dependent cluster resource encounters a critical issue and become offline and the availability group resource is offline until the dependent resource is online.
A critical issue in the cluster turns off the availability group resource.
There is automatic, manual or forced failover in progress for the availability group.
Resolutions
If the SQL server instance of primary replica is down, you can restart and check whether the availability group recovers to healthy state.
If the automatic failover appears to be failed, you can check if a replica has all databases synchronized with the previously known primary then failover to the replica. Otherwise, select a replica with minimum loss of data, recover to failover or forced failover.
If the resource in the cluster is offline while SQL server instances appear to be healthy, you can check the cluster health or any issue using Cluster Manager. You can attempt to turn the availability group resource online using the cluster manager tool.
If there is a failover in progress, wait for the completion.
Home
ENU