Prerequisites for configuring VMware virtual machines for recovery to Azure
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:
Virtual machines with non-english names are not supported for recovery to Azure.
VMware Tools must be installed on the virtual machines.
Ensure that all the ESXi servers of the cluster belong to the same VMware data center.
Enable the UUID for the virtual machines (disk.enableuuid=true). Refer to VMware documentation for details.
If you add new disks, ensure that they are visible from the guest operating system.
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.
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.
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.
Both the source and recovery (target) gateway must have external storage equivalent to 6GB for each virtual machine protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the source and recovery (target) gateway must each have 60GB of external storage.
The minimum size of the external storage must be 50GB.
The maximum number of disks on cloud Replication Gateway depends on the flavor or size of the Replication Gateway. The maximum number of disks supported would be the minimum of the following two:
Maximum number of disks supported for Replication Gateway on source data center.
Maximum number of disks supported for Replication Gateway on target data center.
Resiliency Platform does not support the private endpoint of the storage account.
Make sure that following settings are done:
Allow access from All Network should be checked, OR
If the selected network is specified then you should have proper IP address / CIDR (public IP) of the machine (IMS) using the following setting
Storage accounts > {yourAccount} > Firewalls and Virtual networks.
There should not be any resources on Azure having the same name or substring of name as that of the virtual machine display name or FQHN name on on-premises data center.
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.
More Information