Availability Replica Data Synchronization State
Data synchronization state of some availability database is not healthy.
This policy checks the data synchronization state of the 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.
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:
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.
Possible Solution section is very vague as to be helpful. Should provide additional links to prescriptive steps that are related to the possible causes that are listed in the previous section.
Quite possibly the worst article I have ever read, I am pulling my hair out trying to figure out how to fail over and failback...this isn't nice to do to your DBAs M$.
is this a joke???