Prerequisites for configuring VMware virtual machines for recovery to AWS
Before you run the wizard to configure disaster recovery protection for a resiliency group of VMware virtual machines, ensure that you have met the following prerequisites for the virtualization environment:
VMware Tools must be installed on the virtual machines.
If you add new disks, ensure that they are visible from the guest operating system.
Ensure that all the ESXi servers of the cluster belong to the same VMware data center.
If a virtual machine has more than one ethernet adapter, then all of them should have either static IP configuration or DHCP IP configuration. A mix of static and DHCP IP configuration is not supported on the same virtual machine.
All the virtual disks must be connected to the virtual SCSI controllers. Other controller types are not supported.
The datastores on which the virtual machine disks reside must be accessible to the Replication Gateway on the production data center.
Ensure that the configuration files (vmx files), residing on the datastores, are not located inside a folder. Also the configuration files must not have any special characters in their names.
Though special characters are allowed in a password, you cannot use space in the password.
Configuring resiliency group for remote recovery using Data Mover fails if a virtual machine has snapshots. Hence remove all snapshots before proceeding with the operation.
A maximum of 40 volumes or disks can be attached to the Replication Gateway. The total number of disks from the virtual machines in the resiliency group and the number of disks that are already attached to the gateway should not exceed more than 40. This is a AWS limitation.
Enable the UUID for the virtual machines (disk.enableuuid=true). Refer to VMware documentation for details.
Ensure that the Replication Gateways have sufficient storage to handle the replication for the planned number of protected virtual machines.
Both the on-premises gateway and the cloud gateway must have external storage equivalent to 6GB for each asset protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the on-premises gateway and the cloud gateway must each have 60 GB of external storage.
On Linux virtual machines, ensure that the NIC name in the file matches with the actual NIC name on the system.
On Linux virtual machines, ensure that all the virtual NICs attached to the selected virtual machines have a valid IP address. The IP address may be assigned statically or via DHCP protocol.
A bucket must be created in S3 and must have a policy that assigns the following permissions:
s3:GetBucketLocation and s3:GetObject permissions on the bucket
ec2:ImportSnapshot, ec2:DescribeSnapshots, and ec2:CopySnapshot permissions on all the resources
One role named ImportSnapshotRole must be created and the above policy is associated with this role. The service vmie.amazonaws.com should be able to assume this Role. When you deploy Resiliency Platform through AWS Marketplace, then the required role is automatically created through AWS CloudFormation template.
For more information about the permissions required, refer to the AWS documentation.
If the status of the virtual machine on the recovery data center is not correctly displayed, then you need to refresh the cloud discovery or the virtualization server discovery.
Note:
Resiliency Platform does not support protecting a virtual machine which is created by cloning another VMware virtual machine that is already protected under Veritas Resiliency Platform.