Permanent Failover

Permanent failover is one of the ways to finalize failover. When you perform permanent failover, you permanently switch processes from the source vApp to its replica. As a result, the replica stops acting as a replica and starts acting as the production vApp.


It is recommended that you perform permanent failover if the source vApp and its replica are located in the same site and are nearly equal in terms of resources. In this case, users will not experience any latency in ongoing operations. Otherwise, perform failback.

The permanent failover operation is performed in the following way:

  1. Veeam Backup & Replication removes restore points of the replica from the replication chain and deletes associated files from the datastore. Changes that were written to the delta disks are committed to the replica to bring the replica to the most recent state.
  2. Veeam Backup & Replication removes the replica from the list of replicas in the Veeam Backup & Replication console and the replica becomes the production vApp.
  3. To protect the replica from corruption after permanent failover is complete, Veeam Backup & Replication reconfigures the job or policy and adds the source vApp to the list of exclusions. When replication job starts, the source vApp is skipped from processing. As a result, no data is written to the working replica.

In This Section

Page updated 1/25/2024

Page content applies to build