Volume Replicator uses co-ordinating operations to maintain data consistency by maintaining the same write-order on each Secondary as on the Primary. The Primary Replicator Log volume is time-ordered and contains the data for each individual write. The disk modifications also occur in the same order on the Secondary as on the Primary.

If the Primary recovers after a crash, Volume Replicator locates the last entry in the Primary Replicator Log volume that the Secondary did not acknowledge as successful, before the crash. Updates to this Secondary continue from that point onwards.

When the Primary or the Secondary crashes, the Volume Replicator recovery process ensures that all the pending updates on the Primary are sent to the Secondary in such a way that there is no data loss, and the data is consistent at the end of the recovery. Secondary Replicator Log is used for this purpose.

Volume Replicator is designed to maintain consistency between the Primary RVG and the Secondary RVG even in the event of network failures and the temporary loss of the Primary or Secondary host, or both. When the problem is corrected, and the Primary and Secondary are again both active and able to communicate, the Primary and Secondary automatically resynchronize themselves and continue replication. A Secondary may become temporarily inconsistent during this resynchronization phase. However, because synchronization is achieved in a protected manner, a subsequent network or host failure during this phase cannot cause inconsistency on the Secondary, even if the Primary host is permanently lost.