Matrix of Backup and Restore Strategies for Snapshot or Transactional Replication (by Topology)

More complex replication topologies will generally require a more extensive recovery strategy that includes coordinated backups.

This table shows the recommended recovery strategy for each backup approach and failure situation. The number displayed corresponds to a strategy listed in the key following the table.

Topology/strategy	Publisher fails	Distributor fails	Subscriber fails
Simple replication:
Back up Publisher	2	1	4
Back up Publisher and Distributor	3	3	4
Back up Publisher and Subscriber(s)	2	1	5
Back up Publisher, Distributor, and Subscriber(s)	3	3	5
Distribution database serves multiple Publishers:
Back up Publisher	2	1	4
Back up Publisher and Distributor	3	3	4
Back up Publisher and Subscriber(s)	2	1	5
Back up Publisher, Distributor, and Subscriber(s)	3	3	5
Subscriber database is target of multiple Publishers:
Back up Publisher	2	1	4
Back up Publisher and Distributor	3	3	4
Back up Publisher and Subscriber(s)	N/A	N/A	N/A
Back up Publisher, Distributor, and Subscriber(s)	N/A	N/A	N/A
Database plays role of Publisher and Subscriber:
Back up Publisher	N/A	N/A	N/A
Back up Publisher and Distributor	N/A	N/A	N/A
Back up Publisher and Subscriber(s)	2	1	5
Back up Publisher, Distributor, and Subscriber(s)	3	3	5

Key

There are five basic strategies for recovering snapshot or transactional replication:

Reenable replication.
Restore Publisher database, and then reestablish replication.
Restore Publisher(s) and Distributor, and then validate and reinitialize subscriptions.
Drop and re-create subscription(s).
Restore Subscriber database, and then validate subscriptions.

For more information about these five strategies for recovering snapshot or transactional replication, see Strategies for Restoring Snapshot or Transactional Replication. For more information about replication topologies, see Topology Types.