You can switch back to the primary site after a VM fails over.
When you configure replication from VMware IntelliSnap backups, failback operations are only supported if the IntelliSnap configuration uses the Virtual Server Agent Snap engine. Failback operations are not supported if you use a hardware snapshot engine, regardless of whether the replication operation is performed from a snap copy or a backup copy.
When you perform a failback operation from IntelliSnap backups for a VSA V2 or V1 source VM, the following occurs:
VSA V2 source VM: Deletes or becomes unavailable during a failback operation, but the failback operation completes.
VSA V1 source VM: Deletes or becomes unavailable during a failback operation, but the failback operation fails.
For Azure Stack Hub destinations, you cannot perform failback operations from backup copies.
For destination hypervisors that support failback but not failover groups, perform this operation from the Replication Monitor.
From the navigation pane, go to Disaster recovery > Replication.
The Replication groups page appears.
On the Failover groups tab, in the Name column, click a failover group.
The failover group page appears.
In the upper-right area of the page, click Failback.
A message appears that asks if you want to perform a failback operation.
To confirm that the failback operation can discard all changes that were made for the virtual machine while it was running on the secondary site, select the Discard the changes since failover check box.
If you clear the check box, the undo operation performs a failback, replicating any changes to the virtual machine at the secondary site back to the VM at the primary site.