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 Normal.
- Further operations depend on the location to which the VM is failed back:
- If the VM replica is failed back to a new location, Veeam Backup & Replication additionally reconfigures the replication job and adds the former original VM to the list of exclusions. The VM restored in the new location takes the role of the original VM and is included into the replication job instead of the excluded VM. When the replication job starts, Veeam Backup & Replication will process the newly restored VM instead of the former original VM.
- If the VM replica is failed back to the original location, the replication job is not reconfigured. When the replication job starts, Veeam Backup & Replication will process the original VM in the normal operation mode.
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.