Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In the event that I need to restore a database involved in replication, what considerations to I need to keep in mind?

  • Do I need to keep backups of both the publisher and the subscriber?
  • Can I restore only the publisher and have the subscriber automatically sync up?
  • If the subscriber crashes, is it possible to restore from its back up and have it automatically sync up?
share|improve this question
There's a lot to read: – Jon Seigel Aug 20 '12 at 18:42
Hmm, I searched for something like that on MSDN. – GaTechThomas Aug 20 '12 at 18:49
up vote 5 down vote accepted

The answer depends on your type of replication. For example, merge replication allows you to update in more than one source DB, and then distribute those updates. With this topology, you would of course need backups everywhere data originates.

As for automatic syncing, I've seen that most of the time if there is any issue with repl on either end of publisher / subscriber, you will usually have to reinitialize the repl. An exception to this might be when you have a subscriber problem such that it is offline to the distributor. In that case the distributor would "catch up" the subscriber when it came back up IF there was no corruption (bad sequence) at the subscriber.

As a rule, back everything up, but don't count on being able to "jump-start" repl back to a functional state. Re-initializing it is common, and painful with large DBs.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.