Veeam Backup & Replication 10
Quick Start Guide for Microsoft Hyper-V
Related documents

Performing Failback

You can fail back to a VM in the original or new location. In this section, you will learn how to fail back to the original VM on the source host. For more information on how to do this on another host, see the Performing Failback section in the Veeam Backup & Replication User Guide.

Before You Begin

Make sure that the VM replica for which you want to perform failback is in the Failover state. The replica gets into this state after you perform replica failover.

Performing Failback

To fail back from VM replica to the original VM on the source host, do the following:

  1. In the inventory pane of the Home view, select the Replicas node.
  2. In the working area, right-click the VM replica and select Failback to production to launch the Failback Wizard.

Launch Failback

  1. At the Replicas step of the wizard, click Next.
  2. At the Destination step of the wizard, select Failback to the original VM.

Performing Failback

  1. At the Summary step of the wizard, select the Power on VM after restoring check box and click Finish.

Reference

For more information on failback, see the Replica Failback section in the Veeam Backup & Replication User Guide.

This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VVeeam Backup Enterprise Manager GuideVeeam Agent Management GuideVeeam Cloud Connect GuideVeeam Explorers User GuideVeeam Plug-ins for Enterprise Applications GuideVeeam PowerShell ReferenceVeeam Explorers PowerShell ReferenceVeeam RESTful API ReferenceRequired Permissions for VMware vSphereQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.