About full synchronization of data
Veritas Resiliency Platform uses full synchronization only in the following conditions:
After disaster recovery configuration for a resiliency group:
When Data Mover is configured for a resiliency group, replication is started. At that time, the storage on the target data center must be synchronized with the data from the source data center. This process of synchronizing the entire set of data is a full synchronization.
During Resync operation performed after a recover operation:
A full synchronization is also required after a recover. Recover is an activity initiated by a user when the source data center is down due to a disaster, and the virtual machines need to be brought up at the target data center to provide business continuity. After a recover, the virtual machine runs in the target data center. Once the source data center is back up and running, you must perform a Resync operation from the target data center before you can migrate back to the source data center. This Resync operation launches a full synchronization to synchronize the data on the source data center with the data in the target data center. When the synchronization completes, the source data center is up-to-date. You can then perform the Migrate operation.
The amount of time that is required for full synchronization depends on several factors. These factors include the size of the replication disks, the network bandwidth of the LAN and WAN environment, and the amount of I/O occurring during the synchronization. After the full synchronization is complete, the replication moves into active state. In the active state, Data Mover maintains write-order fidelity.
If the replication state is Syncing, you can view the status of data replication on the resiliency group details page. The progress is displayed on a status bar with percentage complete information. Time required to sync the data is also displayed on this page.
See Viewing resiliency group details.
At times, you need to manually invoke a full synchronization to resume replication after a disk failure or infrastructure failure. For more information on conditions where a full synchronization is required:
See Admin Wait state codes .
More Information
About synchronization used by Resiliency Platform Data Mover