Replication From a Protected Site vCloud Director to AWS
You can protect a vCD vApp to Amazon Web Services (AWS).
When creating a VPG from vCloud Director to AWS the data is stored in S3 and all replicated data from protected virtual machines to AWS is encrypted in S3. All recovery operations bring up the recovered machines in EC2 in 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.
■ 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:
■ For Linux, AWS supports virtual machines with up to 12 volumes, including the boot volume.
■ For Windows, AWS supports virtual machines with up to 22 volumes, including the boot volume.
■ GBT formatted disks are supported for data volumes only.
■ The following table describes the limitations per Import Method:
Import Method |
OS | AWS Import | zImport for Data Volumes | zImport for all volumes |
Boot Volume | Additional Volume | Boot Volume | Additional Volume | Boot Volumes | Additional Volumes |
Linux | 1 TB | 1 TB | 1 TB | 16 TB | 2047 GiB* | 16 TB |
Windows | 1 TB | 1 TB | 1 TB | 16 TB | 2047 GiB* | 16 TB |
|
■ For the
AWS Import and
zImport for Data Volumes import methods, the
AWS ImportInstance API only supports single volume VMs. The boot volume of the protected virtual machine should not be attached to any other volume to
successfully boot. For more information, see http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ImportInstance.html