 | ||
| Replicator Log protection when Primary and Secondary are connected | ||
|---|---|---|
| Prev | Replicator Log overflow protection - srlprot attribute | Next |
| ||
| Replicator Log protection when Primary and Secondary are connected | ||
|---|---|---|
| Prev | Replicator Log overflow protection - srlprot attribute | Next |
This section explains how Volume Replicator works when the Replicator Log is about to overflow while the Primary and Secondary are connected, for different settings of the srlprot attribute.
Different settings of srlprot attribute when Primary and Secondary are connected are as follows:
srlprot=override, fail, or dcm
New writes are throttled in the operating system of the Primary host until a predetermined amount of space, that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log.
srlprot=autodcm
Volume Replicator activates the DCM, instead of throttling writes. Each data volume in the RVG must have a DCM. If every data volume has a DCM attached to it then by default, the Replicator Log protection is set to the AutoDCM mode.
srlprot=off
Disables Replicator Log protection and allows the Replicator Log to overflow.