Recovery to AWS
Zerto applies a single recovery method that creates an AWS EC2 instance per protected VM volume to convert the S3 objects and write them to a local disk. When all the data has been imported and its disk has been attached to the recovered instance, the instance is terminated.
!
Important:
| • | When performing cross replication (on-Premises > Cloud), Zerto assigns the disk at the lowest SCSI Controller location (x:y} as the boot disk. |
| • | For Linux - The recovery method is based on an official AWS Linux AMI (Amazon Machine Image), into which a script is injected to perform the import. |
| • | For Windows - The recovery method is based on an official AWS on Windows AMI (Amazon Machine Image), into which a script is injected to perform the import. |
| • | To ensure that the recovered instance cannot be accessed from the outside world, a security group is created. During a recovery operation the recovered instance is connected to this security group. All inbound traffic is blocked and only outbound traffic to access the script online is allowed. |
| • | Zerto can set default encryption on the S3 bucket so that all objects are encrypted when they are stored in the bucket. To enable S3 encryption please contact support. |
| • | The default instance type is c5.4xlarge and the AWS EC2 default maximum instance quota is 10. If during the creation of instances the maximum EC2 instance quota is reached, the creation of the next and subsequent instances will be queued, increasing the RTO. If during recovery operations, the ZVM identifies a VPG with the potential to exceed the EC2 instance quota, the user will receive an alert with advice to contact AWS support to increase the service limits in order to improve RTO. |
| • | Each VM is responsible for the import process of a single volume. Therefore, it is recommended to contact AWS and increase the maximum instance quota of the c5.4xlarge instance type to the maximum number of volumes you are planning to failover to AWS at once. |
| • | GPT formatted disks are supported for data volumes only. |
| • | When using this recovery method, each volume is created with EBS disk of type io1 with maximum 1000 EBS Provision IOPS allocated. EBS disk type can be changed post recovery without downtime. For more information, see the relevant AWS documentation. The minimum disk size for io1 is 4GB. |
| • | The default Max EBS Provision IOPS quota in a region across all io1 disks is 40000 EBS Provision IOPS, meaning that with 1000 EBS Provision IOPS per volume, the maximum possible number of volumes is 40. If the Max EBS Provision IOPS quota is reached, the failover process will switch to using slower gp2 disks. An event will notify the user of this, and recommend that the user contact AWS support to increase the Max EBS Provision IOPS quota. |
| • | Temporary disks may be created based on the selected instance size. |
| • | The maximum protected data volume size is 16TB, while the boot volume can be up to 2047GiB. |
| • | 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 2TB or larger, the VM you are using may be limited to a 2047 GiB boot volume size. Non-boot volumes do not have this limitation. See AWS Documentation for more information: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html |
See also:
| • | What is the Zerto Solution? |
| • | The Zerto Solution Architecture |
| • | How Zerto Recovery Works |
| • | Zerto Analytics - Overview and Use |
| • | Zerto Cloud Control - Overview |
| • | Benefits of using the Zerto Solution |
| • | How the Zerto Solution for AWS Works |