Replication Server performs loss detection to determine if any messages could not be recovered after the stable queues were rebuilt.
By checking Replication Server loss-detection messages, you can determine what kind of user intervention, if any, is necessary to restore all data to the system. See the Loss Status column in the output from admin health or admin who, sqm to check for possible data loss.
If all data is available, no intervention is necessary and the replication system can return to normal operations. For example, if you know that the save interval for the route or connection is set for a longer length of time than the failure, you can recover all messages with no intervention. However, if the save interval is not set or is set too low, some messages may be lost.
For example, if Replication Server RS2 detects that replicate data server DS2.RDB has lost data from primary data server DS1.PDB, Replication Server RS1 cannot truncate its queues until you decide how to handle the loss. As a result, RS1 may run out of stable storage. Before a loss is detected (that is, after the Checking Loss message is reported), you can choose to ignore losses for a source and destination pair.