Permanent Failover

In this article

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

    Note

    It is recommended to perform permanent failover if the original 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 snapshots (restore points) of the vApp replica from the snapshot chain and deletes associated files from the datastore.
    2. Veeam Backup & Replication removes the vApp replica from the list of replicas in the Veeam Backup & Replication console and the replica vApp becomes a production vApp.
    3. To protect from corruption after permanent failover is complete the vApp to which you have failed over, Veeam Backup & Replication reconfigures the replication job and adds the original vApp to the list of exclusions. When the replication job starts, the original vApp is skipped from processing. As a result, no data is written to the vApp to which you failed over.

    Related Topics

    Performing Permanent Failover

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.