To confirm failback and finalize recovery of the original VM, you need to commit failback.
When you commit failback, you confirm that you want to get back to the original VM. Veeam Backup & Replication gets back to the normal operation mode and resumes replication activities for the original VM to which you failed back.
The commit failback operation is performed in the following way:
- Veeam Backup & Replication changes the state of the replica from Failback to Ready.
- Further operations depend on whether you have failed back to the original VM or recovered VM:
- If you have failed back to a VM recovered from a backup or replica, Veeam Backup & Replication reconfigures all existing jobs where the original VM is present and adds the original VM to the list of exclusions. The recovered VM takes the role of the original VM and is included into all jobs instead of the excluded VM. When the replication job starts, Veeam Backup & Replication processes the recovered VM instead of the former original VM.
- If you have failed back to the original VM, the replication job is not reconfigured. When the replication job starts, Veeam Backup & Replication still processes the original VM.
During failback commit, the failback protective snapshot that saves the pre-failback state of a VM replica is not deleted. Veeam Backup & Replication uses this snapshot as an additional restore point for VM replica. With the pre-failback snapshot, Veeam Backup & Replication needs to transfer fewer changes and therefore puts less load on the network when replication activities are resumed.