A Failback Operation for a Continuous Replication Pair Fails
Article ID: 64731
Article Type: Troubleshooting
Last Modified:
A failback operation for a continuous replication pair might fail because of changes to the source VM after a failover operation.
Symptoms
A failback operation for a continuous replication pair might fail for any of the following reasons:
The source VM was deleted after the failover operation.
A disk was added to the source VM after the failover operation.
A disk was deleted from the source VM after the failover operation.
Causes
Full sync operations are not supported for failback operations, so if the source VM is changed or deleted after a failover operation, the subsequent failback operation fails.
Resolution
To resolve this issue, you can recover the source VM using one of the following methods.
Perform a Full VM Restore In-Place
If the source VM was deleted, you can recover the VM using a restore operation.
If the source VM was deleted or a disk was added to or removed from the source VM, create a new replication group. In this case, use the destination VM as the source VM, and the original (deleted) source cluster as the destination. The replication operation restores the source VM to the source ESX server with no data loss.
From the navigation pane, go to Disaster recovery > Replication Monitor.
On the Continuous tab, in the row for the original replication pair, click the action button, and then select Stop.
Using the replication wizard, create a new replication group and select the former destination VM as the Content and the former source cluster as the Target. For instructions, see Creating a Replication Group Using the Replication Wizard.