Not Synchronizing. After power surge last night, I realized few availability databases also known as a database replica have an unhealthy data synchronization state. What I mean from unhealthy is that they have a status of Not Synchronizing in SQL Server Management Studio for both primary and all secondary availability group replicas See below According to MSDN documentation here, this issue can be caused by the following The availability replica might be disconnected. Database Was Not Active On Source Server' title='Database Was Not Active On Source Server' />If you are not on the same computer as the SQL Server, you usually need to install the SQL Native Client with the ODBC driver. For SQL Server 2008 R2, that. In the previous two article we have learnt how to Backup and Restore Exchange Server 2013 database using Windows Server Backup. In this article we would be focusing. Image?eid=ka2C00000004K0Q&feoid=00NC0000004Nm9k&refid=0EMC00000008YiZ' alt='Database Was Not Active On Source Server' title='Database Was Not Active On Source Server' />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. To investigate which one of those is relevant in my case, I tried to access the database in SQL Server Management Studio, but received the error similar to the one below The target database, Your. Database, is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online. Microsoft SQL Server, Error 9. I also searched the SQL Server Error. Logs for more information, and found following errors 0. Unknown,Always. On Availability Groups data movement for database Your. Database Was Not Active On Source Server' title='Database Was Not Active On Source Server' />Database has been suspended for the following reason failover from partner Source ID 1 Source string SUSPENDFROMPARTNER. To resume data movement on the databaselt c you will need to resume the database manually. Roland Cakewalk Instrument Definitions. For information about how to resume an availability databaselt c see SQL Server Books Online. Unknown,The recovery LSN 9. Duplicating a Database. This chapter describes how to use the DUPLICATE command to create an independently functioning database copy. This chapter contains the. The 1 SQL Server community and education site, with articles, news, forums, scripts and FAQs. Database Was Not Active On Source Server' title='Database Was Not Active On Source Server' />ID 7. This is an informational message only. No user action is required. Unknown,Error 3. Severity 1. State 1. Unknown,Always. On Availability Groups connection with primary database established for secondary database Your. Database on the availability replica with Replica ID f. This is an informational message only. No user action is required. This information from Error. Logs is quiet useful, as it tells me whats wrong and how I can fix this issue. First, it tells that the attempt was made to connect to the primary availability replica. Barber Adagio For Strings Download on this page. Then, it shows the recovery LSN for the database. And, finally, it tells that the Availability Groups data movement for database has been suspended, and we should manually resume the movement. Solution Resuming data movement on the database manually. To resume data movement on the database manually, I simply execute the following Transact SQL statement on primary and all secondary replicas for the databases that are showing this status. ALTER DATABASE Your. Database SET HADR RESUME. After I issued this statement, the database is successfully synchronized.