Adding a Virtual Machine to an Existing VPG
You can add a virtual machine that is not already included in a VPG, to an existing VPG.
Note: You cannot edit the VPG to add a virtual machine while a backup job is running.
Only virtual machines with a maximum of 60 disks can be protected.
60 disks requires 4 SCSI controllers each with a maximum of 15 disks.
When the recovery site is AWS: Only virtual machines that are supported by AWS can be protected by Zerto Virtual Replication. Refer to AWS documentation for the supported operating systems.
Each machine that you intend to protect must have at least 250MB free space because AWS adds files to the recovered machines during failover, move, test failover, and clone operations.
Protected volumes are recovered in EC2 as EBS disks with magnetic disk type. Virtual machines with disks that are less than 1GB are recovered with disks of 1GB. Additional volumes might be created in the recovered instance, dependent on the instance type used for the recovery. These volumes can be ignored.
Note: By default, every m3.xlarge instance is created with two SSD disks. These disks are in addition to the disks associated with each protected virtual machine.
A VPC must exist, and a security group and subnet must be assigned to it and to all other VPCs you want to use for recovered virtual machines.
The following limitations apply when protecting to AWS:
■ You cannot protect machines that have a disk larger than 1TB.
■ AWS supports virtual machines running a Windows operating system with up to 26 volumes, including the boot disk.
■ AWS supports virtual machines running a Linux operating system with up to 40 volumes, including the boot disk.
■ Protected virtual machines running a Linux operating system with more than 1 volume cannot be failed back from AWS after a failover or move operation.
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. During synchronization, you cannot perform any task that requires the protected and recovery sites to be synchronized, such as adding a checkpoint or failing the VPG. You can, however, make changes to the VPG definition, as described in
Editing a VPG.
Note: Adding a virtual machine to a VPG results in all checkpoints being removed and new ones are not added until the added virtual machine is synchronized.
To add a virtual machine to an existing VPG via the VPG definition:
1. In the VPGs tab in the Zerto User Interface, select the VPG and click MORE > Edit VPG. You can also select the VPG to display the VPG details and click EDIT VPG.
The Edit VPG wizard is displayed, enabling you to edit the VPG, including adding and removing virtual machines from the VPG.
2. In the VMs step, select the virtual machine that will be part of this VPG and click the arrow pointing right to include this machine in the VPG. If you want to define the boot order of the VPGs, click DEFINE BOOT ORDER.
3. Configure the virtual machine configuration.
4. Click DONE.
The virtual machine is added to the VPG. This process may take a few minutes. The protected and recovery sites are then synchronized so that the recovery site includes the replication of the added virtual machine in the VPG. After synchronization, the delta changes to the virtual machine are sent to the recovery site.
If the virtual machine is added to a VPG replicating to resource pool in VMware vSphere environments, Zerto Virtual Replication checks that the additional virtual machine doesn’t exceed the resource pool capacity, such that the sum of the virtual machine reservation is less than or equal to the resource pool CPU and storage settings.
You configure the virtual machine in the VPG in the same way that you configured the other virtual machines in the VPG, when you created the VPG, including the storage and NICS.