The failover operation conducts the following steps:

    • Stops replication of all VM disks in the Protected Domain via the secondary disk.
    • AROVA uses the latest VM properties from the CDB and configured failover runbook settings to create VMs in the secondary region and attach secondary disks.
    • VMs in a Recovery Group are created and started in the configured sequence with the defined boot delays, as defined by the failover runbook.

Failover can be triggered in two ways: (1) failover due to disaster and (2) planned failover. In failover due to disaster, the primary region is unavailable due to an unexpected event and workloads are recovered to the secondary region. Planned failover, on the other hand, allows the user to intentionally switch workloads gracefully from the primary region to the recovery region in a controlled and scheduled manner.

Failover can be conducted in response to various different failure scenarios.

See:

Failover Due to Disaster

Planned Failover