Strategies for Backing Up and Restoring Snapshot and Transactional Replication
Applies to: 
SQL Server
Azure SQL Database
When you design a backup and restore strategy for snapshot and transactional replication, there are three areas to consider:
- Which databases to back up.
- Backup settings for transactional replication.
- The steps that are required to restore a database. These depend on the type of replication and options chosen.
This topic covers each of these areas in the next three sections. For information about backup and restore for Oracle publishing, see Backup and Restore for Oracle Publishers.
Note
Azure SQL Managed Instance can be a publisher, distributor, and subscriber for snapshot and transactional replication. Databases in Azure SQL Database can only be push subscribers for snapshot and transactional replication. For more information, see Transactional replication with Azure SQL Database and Azure SQL Managed Instance.
Backing up Databases
For snapshot and transactional replication, you should regularly back up the following databases:
The publication database at the Publisher.
The distribution database at the Distributor.
The subscription database at each Subscriber.
The master and msdb system databases at the Publisher, Distributor and all Subscribers. These databases should be backed up at the same time as each other and the relevant replication database. For example, back up the master and msdb databases at the Publisher at the same time that you back up the publication database. If the publication database is restored, make sure that the master and msdb databases are consistent with the publication database with regard to replication configuration and settings.
If you perform regular log backups, any replication-related changes should be captured in the log backups. If you do not perform log backups, a backup should be performed whenever a setting relevant to replication is changed. For more information, see Common Actions Requiring an Updated Backup.
Backup Settings for Transactional Replication
Transactional replication includes using the sync with backup option, which can be set on the distribution database and the publication database:
We recommend that you always set this option on the distribution database.
Setting this option on the distribution database ensures that transactions in the log of the publication database will not be truncated until they have been backed up at the distribution database. The distribution database can be restored to the last backup, and any missing transactions are delivered from the publication database to the distribution database. Replication continues unaffected.
Setting this option on the distribution database does not affect replication latency. However, the option will delay the truncation of the log on the publication database until the corresponding transactions in the distribution database have been backed up. (This can create a larger transaction log in the publication database.)
We recommend that you set this option on the publication database if your application can tolerate additional latency.
Setting this option on the publication database ensures that transactions are not delivered to the distribution database until they are backed up at the publication database. The last publication database backup can then be restored at the Publisher without any chance of the distribution database having transactions that the restored publication database does not have.
Latency and throughput are affected because transactions cannot be delivered to the distribution database until they have been backed up at the Publisher. For example, if the transaction log is backed up every five minutes, there is an additional five minutes of latency between when a transaction is committed at the Publisher and when the transaction is delivered to the distribution database, and subsequently the Subscriber.
Note
The sync with backup option ensures consistency between the publication database and the distribution database, but the option does not guarantee against data loss. For example, if the transaction log is lost, transactions that have been committed since the last transaction log backup will not be available in the publication database or the distribution database. This is the same behavior as a nonreplicated database.
Setting the sync with backup option on distribution database is not compatible when publisher database is part of availability group. This could lead to following error when log reader agent runs after failover.
The process could not execute 'sp_repldone/sp_replcounters' on 'machinename\instance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Get help: http://help/MSSQL_REPL20011 Possible inconsistent state in the distribution database: dist_backup_lsn {nnnnnnnn:nnnnnnnn:nnnn}, dist_last_lsn {nnnnnnnn:nnnnnnnn:nnnn}. Execute "sp_repldone NULL, NULL, 0, 0, 1", and then execute sp_replflush. Reinitialize all subscriptions to the publication. (Source: MSSQLServer, Error number: 18846)
To set the sync with backup option
- Replication Transact-SQL programming: Enable Coordinated Backups for Transactional Replication (Replication Transact-SQL Programming)
Restoring Databases Involved in Replication
You can restore all databases in a replication topology if recent backups are available and the appropriate steps are followed. The restore steps for the publication database depend on the type of replication and options that are used; however, the restore steps for all other databases are independent of the type and options.
Replication supports restoring replicated databases to the same server and database from which the backup was created. If you restore a backup of a replicated database to another server or database, replication settings cannot be preserved. In this case, you must re-create all publications and subscriptions after backups are restored.
Publisher
There are restore steps provided for the following types of replication:
Snapshot replication
Read-only transactional replication
Transactional replication with updating subscriptions
Peer-to-peer transactional replication
The restore of the msdb and master databases, which are also covered in this section, is the same for all four types.
Publication Database: Snapshot Replication
Restore the latest backup of the publication database. Go to step 2.
Does the publication database backup contain the latest configuration for all publications and subscriptions? If yes, the restore is completed. If no, go to step 3.
Remove the replication configuration from the Publisher, Distributor and Subscribers, and then re-create the configuration. Restore is completed.
For more information about how to remove replication, see sp_removedbreplication (Transact-SQL).
Publication Database: Read-Only Transactional Replication
Restore the latest backup of the publication database. Go to step 2.
Was the sync with backup setting enabled on the publication database before the failure? If yes, go to step 3; if no, go to step 5.
If the setting is enabled, the query
SELECT DATABASEPROPERTYEX('<PublicationDatabaseName>', 'IsSyncWithBackup')returns '1'.Is the restored backup complete and up-to-date? Does it contain the latest configuration for all publications and subscriptions? If yes, the restore is completed. If no, go to step 4.
The configuration information in the restored publication database is not up-to-date. Therefore, you must make sure that the Subscribers have all outstanding commands in the distribution database, and then drop and re-create the replication configuration.
Run the Distribution Agent until all Subscribers are synchronized with the outstanding commands in the distribution database. Verify that all commands are delivered to Subscribers by using the Undistributed Commands tab in Replication Monitor or by querying the MSdistribution_status view in the distribution database. Go to step b.
For more information about how to run the Distribution Agent, see Start and Stop a Replication Agent (SQL Server Management Studio) and Replication Agent Executables Concepts.
For more information about how to verify commands, see View Replicated Commands and Other Information in the Distribution Database (Replication Transact-SQL Programming) and View information and perform tasks using Replication Monitor.
Remove the replication configuration from the Publisher, Distributor and Subscribers, and then re-create the configuration. When you re-create subscriptions, specify that the Subscriber already has the data. The restore is completed.
For more information about how to remove replication, see sp_removedbreplication (Transact-SQL).
For more information about how to specify that the Subscriber already has the data, see Initialize a Subscription Manually.
The sync with backup option was not set on the publication database. Therefore, transactions that were not included in the restored backup might have been delivered to the Distributor and Subscribers. You must now make sure that Subscribers have all outstanding commands in the distribution database, and then manually apply to the publication database any transactions that are not included in the restored backup.
Important
Performing this process can cause published tables to be restored to a point in time that is more recent than the point in time of other nonpublished tables that are restored from the backup.
Run the Distribution Agent until all Subscribers are synchronized with the outstanding commands in the distribution database. Verify that all commands are delivered to Subscribers by using the Undistributed Commands tab in Replication Monitor or by querying the MSdistribution_status view in the distribution database. Go to step b.
For more information about how to run the Distribution Agent, see Start and Stop a Replication Agent (SQL Server Management Studio) and Replication Agent Executables Concepts.
For more information about how to verify commands, see View Replicated Commands and Other Information in the Distribution Database (Replication Transact-SQL Programming) and View information and perform tasks using Replication Monitor.
Use the tablediff utility or another tool to manually synchronize the Publisher with the Subscriber. This enables you to recover data from the subscription database that was not contained in the publication database backup. Go to step c.
For more information about the tablediff utility, see Compare Replicated Tables for Differences (Replication Programming).
Is the restored backup complete and up-to-date? Does it contain the latest configuration for all publications and subscriptions? If yes, execute the sp_replrestart stored procedure to resynchronize the Publisher metadata with the Distributor metadata. The restore is completed. If no, go to step d.
Remove the replication configuration from the Publisher, Distributor and Subscribers, and then re-create the configuration. When you re-create subscriptions, specify that the Subscriber already has the data. The restore is completed.
For more information about how to remove replication, see sp_removedbreplication (Transact-SQL).
For more information about how to specify that the Subscriber already has the data, see Initialize a Subscription Manually.
Publication Database: Transactional Replication with Updating Subscriptions
Restore the latest backup of the publication database. Go to step 2.
Run the Distribution Agent until all Subscribers are synchronized with the outstanding commands in the distribution database. Verify that all commands are delivered to Subscribers by using the Undistributed Commands tab in Replication Monitor, or by querying the MSdistribution_status view in the distribution database. Go to step 3.
For more information about how to run the Distribution Agent, see Start and Stop a Replication Agent (SQL Server Management Studio) and Replication Agent Executables Concepts.
For more information about how to verify commands, see View Replicated Commands and Other Information in the Distribution Database (Replication Transact-SQL Programming) and View information and perform tasks using Replication Monitor.
If you are using queued updating subscriptions, connect to each Subscriber and delete all rows from the MSreplication_queue (Transact-SQL) table in the subscription database. Go to step 4.
Note
If you are using queued updating subscriptions and any tables contain identity columns, you must make sure that the correct identity ranges are assigned after a restore. For more information, see Replicate Identity Columns.
You must now make sure that Subscribers have all outstanding commands in the distribution database, and then manually apply to the publication database any transactions that are not included in the restored backup.
Important
Performing this process can cause published tables to be restored to a point in time that is more recent than the point in time of other nonpublished tables that are restored from the backup.
Run the Distribution Agent until all Subscribers are synchronized with the outstanding commands in the distribution database. Verify that all commands are delivered to Subscribers by using Replication Monitor or by querying the MSdistribution_status view in the distribution database. Go to step b.
Use the tablediff Utility or another tool to manually synchronize the Publisher with the Subscriber. This enables you to recover data from the subscription database that was not contained in the publication database backup. Go to step c.
For more information about the tablediff utility, see Compare Replicated Tables for Differences (Replication Programming).
Is the restored backup complete and up-to-date? Does it contain the latest configuration for all publications and subscriptions? If yes, execute the sp_replrestart stored procedure to resynchronize the Publisher metadata with the Distributor metadata. The restore is completed. If no, go to step d.
Remove the replication configuration from the Publisher, Distributor and Subscribers, and then re-create the configuration. When you re-create subscriptions, specify that the Subscriber already has the data. The restore is completed.
For more information about how to remove replication, see and sp_removedbreplication (Transact-SQL).
For more information about how to specify that the Subscriber already has the data, see Initialize a Subscription Manually.
Publication Database: Peer-to-Peer Transactional Replication
In the following steps, publication databases A, B, and C are in a peer-to-peer transactional replication topology. Databases A and C are online and functioning properly; database B is the database to be restored. The process described here, especially steps 7, 10, and 11, is very similar to the process required to add a node to a peer-to-peer topology. The most straightforward way to perform these steps is to use the Configure Peer-to-Peer Topology Wizard, but you can also use stored procedures.
Run the Distribution Agents to synchronize the subscriptions at databases A and C. Go to step 2.
For more information about how to run the Distribution Agent, see Start and Stop a Replication Agent (SQL Server Management Studio) and Replication Agent Executables Concepts.
If the distribution database that B uses is still available, run Distribution Agents to synchronize subscriptions between databases B and A and databases and B and C. Go to step 3.
Remove metadata from the distribution database that B uses by executing sp_removedistpublisherdbreplication at the distribution database for B. Go to step 4.
At databases A and C, drop the subscriptions to the publication at database B. Go to step 5.
For more information about how to drop subscriptions, see Subscribe to Publications.
Perform a log backup or full backup of database A. Go to step 6.
Restore the backup of database A at database B. Database B now has the data from database A, but not the replication configuration. When you restore a backup to another server, replication is removed; therefore, replication has been removed from database B. Go to step 7.
Re-create the publication at database B, and then re-create subscriptions between databases A and B. (Subscriptions that involve database C are handled at a later stage.).
Re-create the publication at database B. Go to step b.
Re-create the subscription at database B to the publication at database A, specifying that the subscription should be initialized with a backup (a value of initialize with backup for the
@sync_typeparameter of sp_addsubscription). Go to step c.Re-create the subscription at database A to the publication at database B, specifying that the Subscriber already has the data (a value of replication support only for the
@sync_typeparameter of sp_addsubscription). Go to step 8.
Run the Distribution Agents to synchronize the subscriptions at databases A and B. If there are any identity columns in published tables, go to step 9. If not, go to step 10.
After the restore, the identity range that you assigned for each table in database A would also be used in database B. Make sure that the restored database B has received all changes from the failed database B that were propagated to database A and database C; and then reseed the identity range for each table.
Execute sp_requestpeerresponse at database B and retrieve the output parameter
@request_id. Go to step b.By default, the Distribution Agent is set to run continuously; therefore, tokens should be sent to all nodes automatically. If the Distribution Agent is not running in continuous mode, run the agent. For more information, see Replication Agent Executables Concepts or Start and Stop a Replication Agent (SQL Server Management Studio). Go to step c.
Execute sp_helppeerresponses, providing the
@request_idvalue retrieved in step b. Wait until all nodes indicate they have received the peer request. Go to step d.Use DBCC CHECKIDENT to reseed each table in database B to make sure that an appropriate range is used. Go to step 10.
For more information about how to manage identity ranges, see the "Assigning ranges for manual identity range management" section of Replicate Identity Columns.
At this point, database B and database C are not directly connected, but they will receive changes through database A. If the topology contains any nodes that are running SQL Server 2005 (9.x), go to step 11; otherwise, go to step 12.
Quiesce the system, and then re-create the subscription between databases B and C. Quiescing a system involves stopping activity on published tables at all nodes and making sure of that each node has received all changes from all other nodes.
Stop all activity on published tables in the peer-to-peer topology. Go to step b.
Execute sp_requestpeerresponse at database B and retrieve the output parameter
@request_id. Go to step c.By default, the Distribution Agent is set to run continuously; therefore, tokens should be sent to all nodes automatically. If the Distribution Agent is not running in continuous mode, run the agent. Go to step d.
Execute sp_helppeerresponses, providing the
@request_idvalue retrieved in step b. Wait until all nodes indicate they have received the peer request. Go to step e.Re-create the subscription at database B to the publication at database C, specifying that the Subscriber already has the data. Go to step b.
Re-create the subscription at database C to the publication at database B, specifying that the Subscriber already has the data. Go to step 13.
Re-create the subscription between databases B and C:
At database B, query the MSpeer_lsns table to retrieve the log sequence number (LSN) of the most recent transaction that database B has received from database C.
Re-create the subscription at database B to the publication at database C, specifying that the subscription should be initialized based on LSN (a value of initialize from lsn for the
@sync_typeparameter of sp_addsubscription). Go to step b.Re-create the subscription at database C to the publication at database B, specifying that the Subscriber already has the data. Go to step 13.
Run the Distribution Agents to synchronize the subscriptions at databases B and C. The restore is completed.
msdb Database (Publisher)
Restore the latest backup of the msdb database.
Is the restored backup complete and up-to-date? Does it contain the latest configuration for all publications and subscriptions? If yes, recovery is completed. If no, go to step 3.
Re-create the subscription cleanup job from your replication scripts. Recovery is completed.
master Database (Publisher)
Restore the latest backup of the master database.
Make sure that the database is consistent with the publication database with regard to replication configuration and settings.
Databases at the Distributor
Distribution Database
Restore the latest backup of the distribution database.
Was the sync with backup setting enabled on the distribution database before the failure? If yes, go to step 3; if no, go to step 4.
If the setting is enabled, the query
SELECT DATABASEPROPERTYEX('<DistributionDatabaseName>', 'IsSyncWithBackup')returns '1'.Is the restored backup complete and up-to-date? Does it contain the latest configuration for all publications and subscriptions? If yes, recovery is completed. If no, go to step 4.
Either the configuration information in the restored distribution database is not up-to-date, or the sync with backup option was not set on the distribution database. (After the restore, the distribution database might be missing transactions that were committed at the Publisher but have not yet been delivered to Subscribers.) Drop and re-create replication, and then run validation.
Remove the replication configuration from the Publisher, Distributor and Subscribers, and then re-create the configuration. When you re-create subscriptions, specify that the Subscriber already has the data. Go to step b.
For more information about how to remove replication, see sp_removedbreplication (Transact-SQL).
For more information about how to specify that the Subscriber already has the data, see Initialize a Subscription Manually.
Mark all publications for validation. Reinitialize any subscriptions that fail validation. Recovery is completed.
For more information about validation, see Validate Replicated Data. For more information about reinitialization, see Reinitialize Subscriptions.
msdb Database (Distributor)
Restore the latest backup of the msdb database.
Is the restored backup complete and up-to-date? Does it contain the latest configuration for all publications and subscriptions? If yes, recovery is completed. If no, go to step 3.
Remove the replication configuration from the Publisher, Distributor and Subscribers, and then re-create the configuration. When you re-create subscriptions, specify that the Subscriber already has the data. Go to step 4.
For more information about how to remove replication, see sp_removedbreplication (Transact-SQL).
For more information about how to specify that the Subscriber already has the data, see Initialize a Subscription Manually.
Mark all publications for validation. Reinitialize any subscriptions that fail validation. Recovery is completed.
For more information about validation, see Validate Replicated Data. For more information about reinitialization, see Reinitialize Subscriptions.
master Database (Distributor)
Restore the latest backup of the master database.
Make sure that the database is consistent with the publication database with regard to replication configuration and settings.
Databases at the Subscriber
Subscription Database
Is the latest subscription database backup more recent than the minimum distribution retention setting on the distribution database? (This determines whether the Distributor still has all the commands that are required to bring the Subscriber up-to-date.) If yes, go to step 2. If no, reinitialize the subscription. Recovery is completed.
To determine the maximum distribution retention setting, execute sp_helpdistributiondb and retrieve the value from the max_distretention column (this value is in hours).
For more information about how to reinitialize a subscription, see Reinitialize a Subscription.
Restore the latest subscription database backup. Go to step 3.
If the subscription database contains only push subscriptions, go to step 4. If the subscription database contains any pull subscriptions, ask the following questions: Is the subscription information current? Does the database include all tables and options that were set at the time of failure. If yes, go to step 4. If no, reinitialize the subscription. Recovery is completed.
To synchronize the Subscriber, run the Distribution Agent. Recovery is completed.
For more information about how to run the Distribution Agent, see Start and Stop a Replication Agent (SQL Server Management Studio) and Replication Agent Executables Concepts.
msdb Database (Subscriber)
Restore the latest backup of the msdb database. Are pull subscriptions used at this Subscriber? If no, the restore is completed. If yes, go to step 2.
Is the restored backup complete and up-to-date? Does it contain the latest configuration for all pull subscriptions? If yes, recovery is completed. If no, go to step 3.
Drop and re-create the pull subscriptions. When you re-create the subscriptions, specify that the Subscriber already has the data. The restore is completed.
For more information about how to drop subscriptions, see Subscribe to Publications.
For more information about how to specify that the Subscriber already has the data, see Initialize a Subscription Manually.
master Database (Subscriber)
Restore the latest backup of the master database.
Make sure that the database is consistent with the publication database with regard to replication configuration and settings.