Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: 
SQL Server
Follow these guidelines when backing up and restoring:
Ensure the Log Reader Agent isn't running and that no other database activity occurs on the published tables while you're backing up the Publisher.
Back up the Publisher and Distributor at the same time.
Reinitialize all subscriptions if you must restore the Publisher or Distributor.
To restore a Subscriber from a backup without reinitializing subscriptions, the transactions delivered to the distribution database after the last subscription database backup was completed must still be available. The length of time transactions are available depends on distribution retention settings. For information about these settings, see Subscription Expiration and Deactivation.
If a database restore causes the Publisher or Distributor to become out of sync, the replication agents log error messages. You must drop and recreate all relevant publications and subscriptions:
Script the definition of the publications and subscriptions. For more information, see Scripting Replication.
If the definition of the publications changed between the versions of the Publisher and Distributor states, modify the scripts.
Drop the publications and subscriptions.
Run the scripts created in step 1.
If you must drop and reconfigure the Publisher, drop the MSSQLSERVERDISTRIBUTOR public synonym and the configured Oracle replication user by using the CASCADE option to remove all replication objects from the Oracle Publisher.