 | ||
| How data flows in VVR synchronous mode | ||
|---|---|---|
| Prev | Understanding how Veritas Volume Replicator works | Next |
This section explains how VVR processes an incoming write when replicating in synchronous mode.
Figure: Example - how data flows in the synchronous mode of replication shows how data flows in the synchronous mode of replication.
In synchronous mode of replication, VVR processes an incoming write by performing the following steps in the order listed below:
VVR receives a write on the Primary.
Writes it to the Primary SRL.
Sends the write to the Secondary hosts and waits for the synchronous network acknowledgments from the Secondary hosts. At the same time, VVR writes to the data volumes on the Primary.
On the Secondary, VVR receives the write, processes it, and sends a network acknowledgment to the Primary.
Sends writes to the data volumes on the Secondary; when the Primary receives a network acknowledgment from all the Secondary hosts, VVR acknowledges to the application that the write is complete.
Note that the Secondary RVG sends the network acknowledgment as soon as the write is received in the VVR kernel memory. This removes the time required to write to the Secondary data volumes from the application latency. On the Primary, VVR does not wait for data to be written to the Secondary data volumes. This improves application performance. However, VVR tracks all such acknowledged writes that have not been written to the data volumes. VVR can replay these tracked writes if the Secondary crashes before writing to the data volumes on the Secondary or if the Primary crashes before it receives the data acknowledgment.
When the write is written to the data volumes on the Secondary, VVR on the Secondary sends a data acknowledgment to the Primary. VVR marks the write as complete in the SRL when the Primary receives the data acknowledgment from all the Secondary hosts.
When an RDS containing multiple Secondary RVGs is replicating in synchronous mode, the application latency is determined by the slowest Secondary. Overall performance in synchronous mode is determined by the time to write to the SRL, plus the round-trip time required to send data to the Secondary RVG and receive the acknowledgment.
