Configuring Virtual Protection Groups
You protect one or more virtual machines in a VPG. The VPG must include at least one virtual machine. After creating a VPG, you can add or remove virtual machines as required. You can only protect a virtual machine in a VPG when the virtual machine has no more than 60 disks.
VPGs must be created on the protected site; they cannot be created on AWS, the recovery site. The virtual machines on the protected site can be defined under a single hypervisor host or under multiple hosts.
To create a VPG that will be recovered to AWS, you must have a virtual instance in AWS with a Zerto Cloud Appliance installed on it. This virtual instance must be paired with the protected site.
The VPG definition consists of the following:
■ General: A name to identify the VPG and the priority to assign to the VPG.
■ Virtual machines: The list of virtual machines being protected as well as the boot order and boot delay to apply to the virtual protection groups during recovery.
■ Replication: The recovery site settings and the VPG SLA. SLA information includes the default journal history settings and how often tests should be performed on the VPG. These settings are applied to every virtual machine in the VPG but can be overridden per virtual machine, as required.
■ Storage: The default storage volume to use for the recovered virtual machine files and for their data volumes. If a cluster is selected for the host, only storage accessible.
■ Recovery: The networks, subnets, security groups, instance families, and instances types to use for failover/move and failover test procedures and the scripts, if any, that should run at the start or end of a recovery operation.
■ Backup: The properties that govern the VPG backup including the repository where the backups are saved.
■ Summary: The details of the VPG configuration defined in the previous components.