Running Failback

To perform failback for a plan in the FAILOVER state:

  1. Navigate to Recovery Plans.
  2. Select the plan. From the Launch menu, select Continue.

-OR-

Click the plan name to switch to the Plan Details page, and click Continue.

  1. In the Progress Plan window, do the following:
  1. For security purposes, retype your password and click Next.
  2. In the Recovery actions section, do the following:
  1. From the Actions to take drop-down list, choose whether you want to switch from VM replicas to the source VMs immediately or to synchronize the VM disks without actually performing failback.

If you select the Prepare to failback option, Orchestrator will switch from VM replicas to the source VMs when you run the plan next time.

  1. [Applies only if you have selected the Original VM Location] Select the Use quick rollback check box if you want to instruct Orchestrator to synchronize changed data blocks only — this may help you speed up the failback process significantly.

For more information on the quick rollback process, see the Veeam Backup & Replication User Guide, section Quick Rollback.

  1. Choose whether you want the recovered VMs to have the same tags as the source VMs.
  1. In the Recovery Location section, select a location to which VMs will be recovered.

For a recovery location to be displayed in the list of available locations, it must be created and added to the list of inventory items available for the scope, as described in section Managing Recovery Locations.

 

Note

Orchestrator will perform failback using all settings configured for the location — except Instant VM Recovery and backup copy preference. These settings are not applicable to failback operations.

 

If you want to fail back to a new recovery location and the selected location includes multiple hosts, datastores and networks, Orchestrator will use the round-robin algorithm to recover VMs. For more information, see How Orchestrator Places VMs During Failback.

  1. Review configuration information and click Run.

Page updated 11/18/2025

Page content applies to build 13.0.0.1005