Modifying Protected Virtual Machine Volumes

Adding or deleting volumes for a virtual machine protected in a VPG, are automatically reflected in the volumes used for the mirror virtual machine, managed by the VRA in the recovery site.

Adding or deleting a volume in any virtual machine protected in a VPG, causes the journal to be reset as all the checkpoints in the journal are removed.

If you add a volume to the virtual machine, the total number of disks cannot exceed 15 disks per SCSI controller and up to 4 SCSI controllers.

Resizing non-RDM volumes of a virtual machine protected in a VPG are automatically reflected in the volumes used for the mirror virtual machine, managed by the VRA in the recovery site.

Note: If the protected volume is associated with an RDM as a target for replication, the RDM will need to be resized manually, as described in Modifying a Protected RDM Volume.

Changing the defined size of a journal of a virtual machine in a VPG is automatically reflected in the VRA in the recovery site.

When protecting to AWS, if you add a volume to the virtual machine the total number of disks cannot exceed 12, including the boot disk.

To change the recovery datastore for a virtual machine volume, the new datastore must have 45GB or 25% of the storage size for the change to be performed.

If a RDM volume for a protected virtual machine is replicated to an RDM volume in the recovery site and the protected RDM volume is resized, it is not automatically resized in the recovery site.

Note: If the RDM volume is replicated to a VMDK in the recovery site, the recovery site VMDK is automatically resized when the protected site RDM is resized.

To enable protecting a VPG after resizing a protected virtual machine RDM volume:

Note: If the VPG contains more than one virtual machine, remove the protected virtual machine from the VPG, and save the changes. If the VPG contains only one virtual machine, delete the VPG, and, if the virtual machine target disks are of VMDK format, make sure to choose to keep the target disks when the option is displayed.

2. Resize the RDM (both local and remote) as described in the VMware Expanding the size of a Raw Device Mapping (RDM) knowledge base article.

Note: The vCenter will not detect that RDMs were resized unless this procedure is followed.

At this point, the VPG will go through a Delta Sync to compare protected and recovery volumes for changes, and once synchronized, it will enter the Meeting SLA state.