Learn when to use and where to locate the appropriate recovery procedure for partition loss or failure.
Symptom |
Use this procedure |
|---|---|
Replication Server detects lost, damaged, or failed stable queue. |
Recovering from partition loss or failure. |
Message loss occurred because a backlog existed in the failed Replication Server and there were insufficient messages saved at the previous site. |
Message recovery from off-line database logs. |
In addition to message loss, database logs have been truncated. Either the secondary truncation point is invalid or the dbcc settrunc('ltm', 'ignore') command, was executed to truncate log records that have not been transferred by RepAgent to the Replication Server. |
Use the truncated message recovery from the database log to recover the database log. Then use message recovery from off-line database logs to rebuild the stable queues and recover lost messages. |