Prerequisites for configuring Hyper-V virtual machines for recovery to AWS
Before you run the wizard to configure disaster recovery protection for a resiliency group of Hyper-V virtual machines, ensure that you have met the following prerequisites for virtual machine configuration:
If you add new disks, ensure that they are visible from the guest operating system.
Ensure that the integrations services are installed and running inside the virtual machines.
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.
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.
A maximum of 40 volumes or disks can be attached to the cloud Replication Gateway. This is a AWS limitation.
A bucket must be created in S3 and a policy must be created that assigns the following permissions:
s3:GetBucketLocation and s3:GetObject permissions on the bucket
ec2:ImportSnapshot, ec2:DescribeSnapshot, 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.
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.