Replication Server provides you various options for recovering data that is
lost after a component failure in a replication system.
Re-create Subscriptions
Resolve all inconsistencies in the primary version of the data. One way to recover from a failure at a remote site is to re-create the subscriptions.
Database Recovery
When a primary database fails, all committed transactions can be recovered if the database and the transaction log are undamaged. If the database or the transaction log is damaged, you must load a database dump and transaction dumps to bring the database to a known state, and then resubmit the transactions that were executed after the last transaction dump.
Restoring Coordinated Dumps
Restoring database or transaction dumps created by the coordinated dump process returns the primary and replicated data to a previous, consistent state.
Database Resynchronization
Database resynchronization allows you to rematerialize your replicate database and resume further replication without data loss or inconsistency, and without forcing a quiesce of your primary database.