Zerto Import for All Volumes
This method uses the zImport method for all volumes and ensures the fastest RTO.
This method creates an AWS EC2 instance per protected VM volume, called zImporter, to convert the S3 objects and write them to a zImport local disk. When all the data has been imported and its disk have been attached to the recovered instance, the zImport instance is terminated.
■ Temporary disks may be created based on the selected instance size.
■ This import method cannot be used for the recovery of protected virtual machines running Windows Server 2008R2. To support this operating system please contact Zerto support.
■ The maximum protected data volume size is 16TB, while the boot volume can be up to 2047GiB.
Note: 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 When using this import method, if the protected virtual machine using this import method is running Windows 2012, Windows 2012R2 or Windows 2016, the following drivers must be installed on the protected virtual machine before starting recovery operations:
■ Windows PV (Paravirtualization) Drivers
■ Windows ENA (Elastic Network Adapter) Drivers
The following steps must be performed to ensure that the virtual machine will be able to run on the recovery site:
1. Download and Install Windows PV Drivers:
b) Follow the instructions at the site for downloading and installing all the Windows PV Drivers 8.2.0 drivers.
2. Download and Install Windows ENA Drivers:
If you are running Windows 2012 or Windows 2016 on any of the following AWS instance types:
■ C3 | ■ I2 |
■ C4 | ■ R3 |
■ D2 | ■ M4 (excluding M4.16xlarge) |
b) Follow the instructions at the site for downloading and installing the Windows ENA Drivers.
Note: If these drivers are installed on a VM running Windows 2012R2, the other AWS import methods will fail. To overcome this, you must uninstall the drivers before using the other AWS import methods.