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.
When you run Replication Server and Replication Agents in recovery mode, you can replay transactions from reloaded dumps and make sure that all transactions in the primary database are replicated and that no transactions are duplicated. For more information about recovering primary databases from dumps, see Chapter 7, “Replication System Recovery,” in the Replication Server Administration Guide Volume 2.
