Orchestrator provides you a number of options to finalize failover to VM replicas:
- Permanent Failover — as a result, VM replicas in the DR site will no longer be treated as replicas. Restore point snapshots will be deleted, and the source VMs will be removed from replication jobs.
For more information on the permanent failover process, see the Veeam Backup & Replication User Guide, section Permanent Failover.
- Failback — you can choose whether you want to fail back to the original or to a new location.
- In case you fail back to the original location, you will switch from VM replicas back to the source VMs. The source VMs will be restored to the current state of their replicas to apply any changes that occurred to the VM replicas while running in the DR site.
- In case you fail back to a new location, all VM replica files will be transported to the location and used to recover the VMs there. You can use this option if there is no way to use the source VMs (for example, in case the source host becomes permanently unavailable).
Failback is considered to be a temporary stage that must be further finalized. After you test the recovered VMs and make sure these VMs operate correctly, you must either commit failback, or perform the undo failback operation to return the plan back to the FAILOVER state.
For more information on the replica failback process, see the Veeam Backup & Replication User Guide, section Replica Failback.
- [This option becomes available only after you perform the Failback operation]
Commit Failback — this option will finalize failback from VM replicas to the source VMs.
For more information on the commit failback operation, see the Veeam Backup & Replication User Guide, section Commit Failback.
Depending on the selected option, the plan may enter the PERMANENT FAILOVER, FAILBACK, COMMIT FAILBACK or HALTED state. To learn how to work with HALTED replica plans, see Managing Halted Plans.