Introduction to Protecting Virtual Machines : Configuring Virtual Protection Groups
  
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.
When protecting VMs from Azure, you can only protect a virtual machine in a VPG when the virtual machine has no more than 60 disks.
When protecting VMs to Azure, the number of disks attached to the virtual machines should not exceed the quota defined by the instance size set in the VPG and VM settings.
VPGs can be created at the protected site or the recovery site.
Configuring a VPG consists of defining 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. The storage used for the virtual machine definition is also used for the virtual machine data and can be overridden per virtual machine, as required. If a cluster is selected for the host, only storage accessible by every host in the cluster is displayed
Recovery: Recovery details include the networks to use for recovered virtual machines, such as the virtual networks, subnets, network security groups, instance families, and instance size 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.
Retention Status: The retention properties that govern the VPG retention status, including the repository where the repository sets are saved. Retention is relevant only when creating VPGs that will be recovered to Azure. When creating VPGs to be recovered from Azure this tab is not shown.
Summary: The details of the VPG configuration defined in the previous components.
For information about protecting VMs created in Azure see “Protecting Virtual Machines From Azure” on page 30.