Prerequisites for configuring Hyper-V 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.
If you add new disks, ensure that they are visible from the guest operating system.
Ensure that the Hyper-V integrations services are installed and running inside the virtual machines.
If you want to do IP customization, ensure that the Hyper-V virtual machines are updated with the latest Hyper-V integration services.
Ensure that you have disabled the 'Quick removal' policy for disks in Windows Server 2008 R2 and disabled the 'write-cache' policy for disks in Windows Server 2012 R2.
When protecting Hyper-V virtual machines that use Dynamic Memory, ensure that the Maximum RAM value is set to a reasonable value. This value is used to assign the memory size to the virtual machines on the target (recovery) site. If Maximum RAM is set to a very high value then while configuring the resiliency group for remote recovery, the operation may fail.
Enough storage must be available on the recovery data center for provisioning the replicated virtual machines.
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.
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.
A Windows host is already added to resiliency domain using 'Prepare Host for Replication' operation. If you now add a non-initialized data disk to the host on IDE controller, you need to initialize the disk, reboot the host and refresh Hyper-V server before you can protect the host for DR.
More Information