You can incrementally synchronize the Secondary using the Replicator Log overflow protection feature. To enable Replicator Log overflow protection for a Secondary, you can set the log overflow protection for the corresponding Secondary to DCM or AutoDCM. Each data volume in the RVG must have a DCM log associated with it.

If the Replicator Log volume overflows and log overflow protection is set to DCM or AutoDCM, the Secondary does not need to be synchronized completely before it starts replicating again, because the Secondary can be synchronized incrementally. In this case, the DCM log is used and only the updates that are marked on the DCM after the Replicator Log volume overflows are copied to the Secondary. The Secondary is inconsistent during the period when it is updated from the DCM log.