Permanent failover is one of the ways to finalize failover. When you perform permanent failover, you permanently switch processes from the source VM to its replica. As a result of permanent failover, the VM replica stops acting as a replica and starts acting as the production VM.
We recommend you to perform permanent failover only if the source VM 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:
- Veeam Backup & Replication powers off the replica.
- Veeam Backup & Replication removes short-term and long-term restore points of the replica from the replication chain and deletes associated files from the datastore. Changes that were written to the protective virtual disks (<disk_name>-interim.vmdk) are committed to the replica to bring the replica to the most recent state.
- Veeam Backup & Replication removes the replica from the list of replicas in the Veeam Backup & Replication console.
- To protect the replica from corruption after permanent failover is complete, Veeam Backup & Replication reconfigures the current CDP policy by adding the source VM to the list of exclusions. Note that other policies and jobs are not modified automatically. When the CDP policy starts, the source VM is skipped from processing. As a result, no data is written to the working VM replica.