Replica Failback

If you want to resume operation of a production VM, you can fail back to it from a VM replica. When you perform failback, you get back from the VM replica to the original VM, shift your I/O and processes from the target host to the production host and return to the normal operation mode.

If you managed to restore operation of the source host, you can switch from the VM replica to the original VM on the source host. If the source host is not available, you can restore the original VM to a new location and switch back to it. Veeam Backup & Replication offers three failback options:

• You can fail back to a VM in the original location on the source host.
• You can fail back to a VM that has been restored up-front from the backup in a new location.
• You can fail back to an entirely new location by transferring all VM replica files to the selected destination.

The first two options help you decrease recovery time and use of the network traffic: Veeam Backup & Replication needs to transfer only differences between the original VM and VM replica. The third option can be used if there is no way to use the original VM or restore the VM from the backup before performing failback.

How Failback Works

If you fail back to an existing original VM, Veeam Backup & Replication performs the following operations:

1. If the original VM is running, Veeam Backup & Replication powers it off.
2. Veeam Backup & Replication calculates the difference between disks of the original VM and disks of the VM replica in the Failover state. Difference calculation helps Veeam Backup & Replication understand what data needs to be transported to the original VM to synchronize it with the VM replica.
3. Veeam Backup & Replication transports changed data to the original VM.
4. Veeam Backup & Replication powers off the VM replica. The VM replica remains powered off until you commit failback or undo failback.
5. Veeam Backup & Replication creates a failback protective snapshot for the VM replica. The snapshot acts as a new restore point and saves the pre-failback state of the VM replica. You can use this snapshot to return to the pre-failback state of the VM replica afterwards.
6. Veeam Backup & Replication calculates the difference between the VM replica and the original VM once again and transports changed data to the original VM. A new synchronization cycle lets Veeam Backup & Replication copy a portion of last-minute changes made on the VM replica while the failback process was being performed.
7. The state of the VM replica is changed from Failover to Failback. Veeam Backup & Replication temporarily puts replication activities for the original VM on hold.
8. If you have selected to power on the original VM after failback, Veeam Backup & Replication powers on the restored original VM on the target host.

If you fail back to an entirely new location, Veeam Backup & Replication performs the following operations:

1. Veeam Backup & Replication transports all VM replica files and stores them on the target volume.
2. Veeam Backup & Replication registers a new VM on the target host.
3. If you have selected to power on the original VM after failback, Veeam Backup & Replication powers on the restored original VM on the target host.

In Veeam Backup & Replication, failback is considered a temporary stage that should be further finalized. After you test the recovered original VM and make sure it is working without problems, you should commit failback. You can also undo failback and return the VM replica back to the Failover state.

Related Topics

• Supported Platforms for Replica Failback
• Performing Failback