Adding Virtual Machines to a VPG

You can add virtual machines that are not already included in a VPG, to an existing VPG. A virtual machine can be protected in a maximum of three existing VPGs, provided that the VPGs are recovered to different sites.

Protecting virtual machines in several VPGs is enabled only if both the protected site and the recovery site, as well as the VRAs installed on these sites, are of version 5.0 and higher.

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.

■ 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 This is 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 with up to 12 volumes, including the boot disk.

■ You cannot protect virtual machines that are GPT partitioned.

■ Only virtual machines that are supported by Azure can be protected by Zerto Virtual Replication. All Windows operating systems are supported.

Note: Microsoft does not support operating systems that are past the End of Support date, without a Custom Support Agreement (CSA). For more information about Microsoft operating systems support for Microsoft Azure, refer to https://support.microsoft.com/en-us/kb/2721672.

■ For Linux distribution, refer to Azure documentation:

■ Protected volumes are recovered in Azure as VHD disks in a page blob. Virtual machines with disks that are less than 1GB are recovered with disks of 1GB.

Note: For some instance size, the Azure virtual machine is created with a Local SSD disk which is a temporary disk. This disk is in addition to the disks associated with each protected virtual machine.

■ The following limitations apply when protecting to Azure

■ You cannot protect machines that have a disk larger than 1TB.

■ The protected virtual machines needs to have at least one NIC.

■ The supported number of data disks and NICS per virtual machine is dependent on the selected instance size. For example, instance size D3_v2 allows up to eight data disks per virtual machine.

■ To create a VPG that will be recovered to Azure, you must have a virtual machine in Azure with a Zerto Cloud Appliance installed on it. This ZCA must be paired with the protected site.

For additional considerations, see Azure subscription and service limits, quotas and constraints: https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits.

■ 20 cores per subscription

■ 200 Storage accounts per subscription

■ 20 VMs per region per subscription

■ VM per series (Dv2, F, etc.) cores per subscription201 per Region

■ A standard storage account has a maximum total request rate of 20,000 IOPS. The total IOPS across all of your virtual machine disks in a standard storage account should not exceed this limit.

VM Tier	Basic Tier VM	Standard Tier VM
Disk size	1023 GB	1023 GB
Max 8 KB IOPS per persistent disk	300	500
Max number of disks performing max IOPS	66	50