 | ||
| Replicator Log protection when Primary and Secondary are disconnected | ||
|---|---|---|
| Prev | Replicator Log overflow protection - srlprot attribute | Next |
| ||
| Replicator Log protection when Primary and Secondary are disconnected | ||
|---|---|---|
| Prev | Replicator Log overflow protection - srlprot attribute | Next |
This section explains in detail how Volume Replicator works when the Replicator Log is about to overflow while the Primary and Secondary are disconnected for different settings of the srlprot attribute.
Different settings of srlprot attribute when Primary and Secondary are disconnected are as follows:
srlprot=override
Writes by the application to the Primary are allowed to complete even if it overflows the Replicator Log.
srlprot=off
Disables Replicator Log protection and lets the Replicator Log overflow.
srlprot=fail
Writes by the application to the Primary are failed to make sure that the Replicator Log does not overflow.
srlprot=dcm, autodcm
DCM protection is activated and writes are written to the DCM. Each data volume in the RVG must have a DCM.