Troubleshooting: Recover operation
Following are some issues that you may encounter while taking over a resiliency group consisting of virtual machines.
After performing the recover 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.
While taking over 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 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 taking over to the cloud data center if the operation fails after the reverse replication stage, then run the Start resiliency group operation and select the Refresh storage, network, compute and customizations option.
During recover operation, there is an option to abort the recover operation to avoid any data loss. If this option is selected and the operation fails in "Check if host is ready for replication reversal" subtask of "Takeover Replication" step, then check:
Is the connectivity between the source gateway and target gateways 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.