Troubleshooting: Migrate operation
Following are some issues that you may encounter while migrating a resiliency group consisting of virtual machines.
After performing the migrate operation, if the network interface card (NIC) is in disconnected state, you need to connect it manually. This is applicable when you migrate VMware and Hyper-V virtual machines to an on-premises data center and the replication technology is 3rd party.
If the Migrate operation fails while creating the network interface card (NIC) on Azure with the error Could not get IP data for NICs <network card name>, you need to create appropriate network mapping and launch the operation.
While migrating from cloud to on-premises data center, if the migrate operation fails with 'host not added to Infrastructure Management server' error then ensure that the host is added to the cloud IMS.
See Reasons for add host operation failure.
While migrating to the cloud data center if the operation fails before the reverse replication stage, then depending on where you want the virtual machine to be online do one of the following:
Virtual machine should be migrated to target data center: Run the Retry operation.
Virtual machine should remain online on the source data center: Run the Start resiliency group operation and select the Refresh storage, network, compute and customizations option.
While migrating to the cloud data center if the operation fails after the reverse replication stage, then you cannot bring the virtual machines up on the source data centre. You can only bring the virtual machines up on the target data centre. To bring the virtual machines up on the target data center, do one of the following:
Run the Retry operation.
Run the Start resiliency group operation and select the Refresh storage, network, compute and customizations option.
The migrate workflow ensures that there is no data loss during the migrate operation. So there are checks to ensure the data consistency of protected host with VRP Data Mover. If these checks fails then that results in failure and the workflow aborts.
If the migrate operation fails in subtask of step, you should check the following:
Connectivity between the protected host and source gateway.
Whether the protected host was powered off and not shutdown properly.
In such cases perform Start operation and select the Refresh storage, network, compute, and customizations option. Once the protected host is powered on, ensure that the host can communicate to the gateway, and then retry the migrate operation.
If the migrate operation fails in subtask of step, you should check the following:
If the connectivity between the source gateway and target gateways is intact. If the two gateways cannot communicate that implies a probable chance of data loss and so the workflow aborts.
In this case ensure that the two gateways can communicate with each other.