可用性グループ オンライン
This monitor checks the online or offline state of availability group.The monitor is 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.
可用性グループはオフラインであり、使用できません。この問題は、プライマリ レプリカをホストするサーバー インスタンスのエラー、またはオフラインになっている WSFC 可用性グループ リソースによって発生する可能性があります。
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 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.
クラスターの可用性グループ リソースがオフラインになりました。
Any dependent cluster resource encounters a critical issue and become offline and the availability group resource is offline until the dependent resource is online.
クラスターでの重要な問題により、可用性グループ リソースがオフになりました。
There is automatic, manual or forced failover in progress for the availability group.
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.
Target | Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupHealth |
Parent Monitor | System.Health.AvailabilityState |
Category | AvailabilityHealth |
Enabled | True |
Alert Generate | False |
Alert Auto Resolve | False |
Monitor Type | Microsoft.SQLServer.2012.AlwaysOn.SystemPolicyScriptMonitorType |
Remotable | True |
Accessibility | Public |
RunAs | Microsoft.SQLServer.2012.AlwaysOn.MonitoringAccount |
<UnitMonitor ID="Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupOnline" RunAs="Microsoft.SQLServer.2012.AlwaysOn.MonitoringAccount" TypeID="Microsoft.SQLServer.2012.AlwaysOn.SystemPolicyScriptMonitorType" Accessibility="Public" Enabled="true" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Target="AlwaysOnDisc!Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupHealth" Priority="Normal">
<Category>AvailabilityHealth</Category>
<OperationalStates>
<OperationalState ID="Success" MonitorTypeStateID="HealthState" HealthState="Success"/>
<OperationalState ID="Critical" MonitorTypeStateID="ErrorState" HealthState="Error"/>
</OperationalStates>
<Configuration>
<Interval>900</Interval>
<TimeoutSeconds>300</TimeoutSeconds>
<PolicyName>$Target/Property[Type="AlwaysOnDisc!Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupHealth"]/AvailabilityGroupName$-AlwaysOnAgOnlineStateHealthPolicy</PolicyName>
<InstanceName>$Target/Property[Type="AlwaysOnDisc!Microsoft.SQLServer.2012.AlwaysOn.AvailabilityGroupHealth"]/InstanceName$</InstanceName>
</Configuration>
</UnitMonitor>