Prerequisites for configuring virtual machines where source and target data centers are cloud or private cloud
This topic is applicable to Azure stack and Before you run the wizard to configure disaster recovery protection for a resiliency group of virtual machines, ensure that you have met the following prerequisites for the virtualisation environment:
If you add new disks, ensure that they are visible from the guest operating system.
The port required the virtual appliances & host should be open in firewall.
The network security group should be attached to the virtual machines.
Ensure that the resource groups should be unlocked.
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.
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.
Though special characters are allowed in a password, you cannot use space in the password.
Both the source and recovery (target) gateway must have external storage equivalent to 4GB 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 40GB of external storage. The minimum size of the external storage must be 50GB.
In order to persist the iptable rules, ensure IPTABLES_SAVE_COUNTER directive is set to
yesiniptables config fileand iptables service is running.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.
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.
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.
See Managing virtual machines for remote recovery (DR) from Azure to Azure .