Forcing the Synchronization of a VPG
If the protected virtual machines are updated such that they are no longer synchronized with their mirror machines in the recovery site, you can force the resynchronization of the machines. An example of when the machines can be out-of-sync is when there is a rollback of a virtual machine to a VMware snapshot. In this case, the recovery virtual machine will include changes that have been rolled back in the protected machine, so that they are no longer synchronized.
You can force the synchronization of the machines in a VPG to remedy this type of situation.
|
Note:
|
You cannot force the synchronization of a VPG while a retention process is running. |
To forcibly synchronize a VPG:
|
1.
|
In the Zerto User Interface, select the VPGs or VMs tab and click the VPG to display the VPG details. |
|
2.
|
Click MORE > Force Sync. |
|
Note:
|
If the VPG was previously viewed, and the tab for this VPG is still displayed, you can access the details by selecting the tab. |
The VPG starts to synchronize with the recovery site. As the journal fills up during the synchronization, older checkpoints are deleted from the journal to make room for the new data, and the data prior to these checkpoints are promoted to the virtual machine virtual disks.
Thus, during the synchronization, you can recover the virtual machine to any checkpoint still in the journal, but as time progresses, the list of checkpoints available can lessen.
If the journal is not big enough to complete the synchronization without leaving at least ten minutes worth of checkpoints, the synchronization pauses, for the amount of time which is specified in the Replication Pause Time value, for the VPG to enable intervention, to ensure recovery to a checkpoint remains available.
The intervention can be, for example, increasing the size of the journal, or cloning the journal as described in Deleting a VPG.
See also: