For an unknown reason the primary replica is synchronized however the secondary replica was not synchronized? This is a database with few changes because it is being used to configure our application servers before we do a final full backup. The secondary replica was in a restoring mode. Is this normal? Could reboots have caused this loss of data?,... please explain why the synchronization is not fixing the lost data? Or is too much data lost.
When attempting to failover there is a warning of potential data loss.
Error below when clicking on link for replica not synchronizing. We are using auto synch. This is two node SQL AG.
How do we fix the below error? I tried removing the database from the AG then deleted the secondary replica. Next added the database back into the AG and seeded it automatically. It finished but the below error occurred? Synchronization was not occurring on the secondary replica.
Also noticed when deleted the database from the secondary replica that it removes from the UI however it remains on the local drive. Could automatic seeding have failed because these data files were there originally?? But there was no error indicating duplicate database files. In fact the wizard finished.
How do we fix this???
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Data synchronization state of some availability database is not healthy.
availability database is suspended.
At least one availability database on this availability 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.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
dsk