To confirm failback and finalize recovery of the original vApp, you need to commit failback.
When you commit failback, Veeam Backup & Replication gets back to the normal operation mode and resumes replication activities for the original vApp to which you failed back.
The commit failback operation is performed in the following way:
- Depending on whether you have failed back to the original vApp or recovered vApp:
- If you have failed back to a vApp recovered from a backup or replica, Veeam Backup & Replication will reconfigure all existing jobs where the original vApp is present and adds the original vApp to the list of exclusions. The recovered vApp takes the role of the original vApp and is included into all jobs instead of the excluded vApp. When the vCD replication job starts, Veeam Backup & Replication processes the recovered vApp instead of the former original vApp.
- If you have failed back to the original vApp, the vCD replication job is not reconfigured. When the vCD replication job starts, Veeam Backup & Replication still processes the original vApp.
- Veeam Backup & Replication changes the state of the replica from Failback to Ready.
During failback commit, the failback protective snapshot that saves the pre-failback state of a vApp replica is not deleted. Veeam Backup & Replication uses this snapshot as an additional restore point for vApp 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.