After successful SQL AG DB restore database does not get replicated to the secondary replica.

book

Article ID: 100052381

calendar_today

Updated On:

Description

Error Message

In SQL Server Management Studio, the status of the database on primary replica is ‘Synchronized’, whereas on the secondary replicas it is ‘Not Synchronizing’. Database state can be checked on the dashboard under the ‘Synchronization state’. It can also be checked by connecting to master on primary replica and executing the query: 

'select * from sys.dm_hadr_database_replica_states'  

 

Cause

This issue occurs due to limitation with SQL Server 2012 and SQL Server 2014. These versions require eviction of database from Availability Group for synchronization to take place.

 

Resolution

As workaround, get the database back in ‘Synchronized’ state in all nodes using following steps:  

1. Open SQL Server Management Studio and connect to all the nodes. Browse to the availability group in question.

2. In the primary node, remove the database from the AG by selecting ‘Remove Database from Availability group’, if it is present. 

3. Now, delete the database on all secondary replicas. 

4. At this stage, we have the database on primary node only, and it is not part of AG. Right-click the availability group and choose ‘Add database’ option.  

5. Complete the wizard to add the database back into the AG. 

 

There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. While this issue may be resolved in a future major revision of the software at a later time, it is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.

 

Issue/Introduction

Restore job of a SQL 2012 and SQL 2014 database which is part of a SQL Availability group restores data only to the primary replica. The database does not get replicated to the secondary, while the restore job is successful.

Additional Information

ETrack: 4062721