Data synchronization state of some availability database is not healthy

Data synchronization state of some availability database is not healthy

 

Published: May 17, 2016

Updated: May 17, 2016

Applies To: SQL Server 2016

Policy NameAvailability Replica Data Synchronization State
IssueData synchronization state of some availability database is not healthy.
CategoryWarning
FacetAvailability replica

This policy checks the data synchronization state of the availability database (also known as a "database replica"). The policy is in an unhealthy state when the data synchronization state is NOT SYNCHRONIZING or the state is not SYNCHRONIZED for the synchronous-commit database replica.

System_CAPS_ICON_note.jpg Note


For this release of SQL Server 2016, information about possible causes and solutions is located at Data synchronization state of availability database is not healthy on the TechNet Wiki.

At least one availability database on the replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state. This issue can be caused by the following:

  • The availability replica might be disconnected.

  • The data movement might be suspended.

  • The database might not be accessible.

  • There might be a temporary delay issue due to network latency or the load on the primary or secondary replica.

Resolve any connection or data movement suspend issues. Check the events for this issue using SQL Server Management Studio, and find the database error. Follow the troubleshooting steps for the specific error.

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

Community Additions

ADD
Show:
© 2016 Microsoft