| title | Availability group is not ready for automatic failover | |
|---|---|---|
| description | Learn how to identify possible reasons why an Always On availability group is not ready for failover. | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| ms.date | 05/17/2016 | |
| ms.service | sql | |
| ms.subservice | availability-groups | |
| ms.topic | reference | |
| f1_keywords |
|
|
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
- Policy Name: Availability Group Automatic Failover Readiness
- Issue: Availability group is not ready for automatic failover.
- Category: Critical
- Facet: Availability group
This policy checks to verify that the availability group has at least one secondary replica that is failover ready. The policy is in an unhealthy state and an alert is raised when the failover mode of the primary replica is automatic, however none of the secondary replicas in the availability group are failover ready.
The policy is in a healthy state when at least one secondary replica is automatic failover ready.
The availability group is not ready for automatic failover. The primary replica is configured for automatic failover; however, the secondary replica is not ready for automatic failover. The secondary replica that is configured for automatic failover might be unavailable or its data synchronization state is currently not SYNCHRONIZED.
Following are possible solutions for this issue:
-
Verify that at least one secondary replica is configured as automatic failover. If there is not a secondary replica configured as automatic failover, update the configuration of a secondary replica to be the automatic failover target with synchronous commit.
-
Use the policy to verify that the data is in a synchronization state and the automatic failover target is SYNCHRONIZED, and then resolve the issue at the availability replica.
Overview of Always On Availability Groups (SQL Server)
Use the Always On Dashboard (SQL Server Management Studio)