Adding Virtual Machines to a VPG - Overview
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. |
|
•
|
You cannot add a virtual machine in an existing VPG, while a retention process 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. |
For AWS or Azure recovery sites, see the following topics:
Adding Virtual Machines to a VPG - When the Recovery Site is AWS
|
•
|
Only virtual machines that are supported by AWS can be protected by Zerto. Refer to AWS documentation for the supported operating systems. |
|
•
|
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. |
|
•
|
AWS allocates EBS volumes by multiplications 1 GiB. When recovering VMs to AWS, whose volume sizes are not multiplications of GiB, AWS rounds the recovered volumes to the closest GiB, resulting in a size mismatch between the recovered and protected volumes. In this case, the original protected disks cannot be used for preseed and the VMs are recovered in Needs Configuration state. |
|
•
|
The following limitations apply when protecting to AWS: |
|
•
|
For Linux, AWS supports virtual machines with up to 40 volumes, including the boot volume. |
|
•
|
For Windows, AWS supports virtual machines with up to 26 volumes, including the boot volume. |
|
•
|
Note that C5/M5 instances have 28 available devices and each volume/NIC utilizes one device. Windows supports up to 26 volumes. For more information, see Elastic Network Interfaces. |
| OS |
Boot Volumes |
Additional Volumes |
| Linux
|
2047 GiB* |
16 TB |
| Windows
|
2047 GiB* |
16 TB |
| * Some VMs use the MBR partitioning scheme, which only supports up to 2047 GiB boot volumes. If your instance does not boot with a boot volume that is 2 TB or larger, the VM you are using may be limited to a 2047 GiB boot volume. See the relevant AWS documentation for more information: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html |
It is strongly recommended to perform a Failover Test to ensure that the recovered instance is successfully running on AWS.
Adding Virtual Machines to a VPG - When the Recovery Site is Azure
For complete and detailed requirements, see Zerto Virtual Replication Azure Enterprise Guidelines.
See also: