Editing a VPG

You can edit a VPG definition, including adding virtual machines to the VPG, as described in Adding a Virtual Machine to an Existing VPG, deleting virtual machines from the VPG, or changing the information about how virtual machines are recovered, such as adding or removing volumes from the virtual machine.

After modifying the VPG, the definition is updated. While the VPG definition is being updated, you cannot perform any operations on the VPG, such as adding a checkpoint, editing the VPG properties, or failing the VPG. After the definition is updated, the VPG is synchronized with the recovery site, and during this time you cannot perform any task that requires the protected and recovery sites to be synchronized together, such as adding a checkpoint or failing the VPG. You can however make changes to the VPG definition, such as changing the history that is maintained as long as the data requirements for the VPG or any of the virtual machines in the VPG are not changed. If you change the storage requirements for any of the virtual machines in the VPG, the VPG definition is re-updated and the synchronization process is restarted.

Note: Synchronization after adding a virtual machine volume to, or removing a virtual machine volume from, a virtual machine in the VPG results in all checkpoints being removed and the checkpoint mechanism restarts after synchronization completes.

1. In the Zerto User Interface, in the VPGs tab select the VPG to be edited and click MORE > Edit VPG. You can also select the VPG, display the VPG details, and click Edit VPG.

2. Make any required changes to the VPG definition, as described in To create a virtual protection group (VPG):. You can jump directly to a step to make a change in that step, for example, the REPLICATION step or the RECOVERY step, by clicking the step. Steps that have been completed are marked with a tick.

Note: If the Journal Size Hard Limit or Journal Size Warning Threshold in the advanced journal settings for the VPG SLA settings, or the default values are changed, the changed values are not applied to existing virtual machines but only to new virtual machines added to the VPG.

When a virtual machine is removed from a VPG, a warning is displayed. Another message is displayed when trying to save the VPG, whether to save the recovery volumes or not, which can be used for preseeding, if the virtual machine is added back to the VPG.

The VPG is updated and then synchronized with the recovery site, if required, for example when the host was changed.

Note: Synchronization after deleting a virtual machine from a VPG results in all checkpoints being removed and the checkpoint mechanism restarts after synchronization completes.

Changing a recovery Org vDC when recovering to vCD, results in an initial synchronization, resulting in all the checkpoints being deleted.

If the journal size hard limit is reduced, and if the current size is greater than the newly defined size, the journal remains at the current size. When the amount of the journal used falls below the hard limit value it will not grow greater than the new hard limit. Unused journal volumes from the added volumes are marked for removal and removed after the time equivalent to three times the amount specified for the journal history, or twenty-four hours, whichever is more.

Note: If the Journal Size Hard Limit or Journal Size Warning Threshold in the VPG SLA settings are changed, the changed values are not applied to existing virtual machines but only to new virtual machines added to the VPG.