Modifying Protected Virtual Machine Volumes
The following topics are described in this section:
Adding or deleting volumes for a virtual machine protected in a VPG, is automatically reflected in the volumes used for the mirror virtual machine, managed by the VRA in the recovery site.
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.
Adding a volume in an any virtual machine, protected in a VPG, causes a new checkpoint to be added, to mark the action.
When adding 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 for Linux machines and 22 for Windows machines, including the boot disk.
See also: