Recovering from RSSD failure

If you cannot recover the most recent database state of the RSSD, recovering from an RSSD failure is a complex process. In this case, you must load the RSSD from old database dumps and transaction log dumps.

NoteIt is not possible to migrate an RSSD database across platforms using commands such as, cross-platform dump and load, or bcp. To migrate, you must rebuild the replication system on the new platform.

The procedure for recovering an RSSD is similar to that for recovering a primary database. However, it requires more steps, since the RSSD holds information about the replication system itself. RSSD system tables are closely associated with the state of the stable queues and of other RSSDs in the replication system.

If a Replication Server RSSD has failed, you first need to determine the extent of recovery required. To do this, perform one or more of the following actions: