Skip to content

Latest commit

 

History

History
51 lines (39 loc) · 2.61 KB

File metadata and controls

51 lines (39 loc) · 2.61 KB
title Availability group is not ready for automatic failover | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology high-availability
ms.topic conceptual
f1_keywords
sql12.swb.agdashboard.agp3autofailover.issues.f1
helpviewer_keywords
Availability Groups [SQL Server], policies
ms.assetid 28261014-342c-442a-bd89-6d04b8d4e8b7
author MashaMSFT
ms.author mathoma
manager craigg

Availability group is not ready for automatic failover

Introduction

Policy Name Availability Group Automatic Failover Readiness
Issue Availability group is not ready for automatic failover.
Category Critical
Facet Availability group

Description

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.

Note

For this release of [!INCLUDEssCurrent], information about possible causes and solutions is located at Availability group is not ready for automatic failover on the TechNet Wiki.

Possible Causes

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.

Possible Solutions

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.

See Also

Overview of AlwaysOn Availability Groups (SQL Server)
Use the AlwaysOn Dashboard (SQL Server Management Studio)