The Protected Domain failover operation transfers workloads between primary and secondary regions in the event of failure or planned maintenance activities. This ensures business continuity by minimizing downtime and maintaining access to critical virtual machines and services. The failover operation can apply to all VMs of a Protected Domain, selectively to impacted VMs of a Protected Domain, or even to AROVA itself depending upon the failure scenario. Key things to know about failover:

    • The Protected Domain is the fundamental unit of failover. Only VMs belonging to a Protected Domain can be failed over.
    • Failover operations are fully orchestrated by AROVA.
    • AROVA can be run on primary or secondary sites.

Protection of AROVA itself and protection of production VMs are independent from one another. If AROVA experiences a failure in both of its zones while production VMs remain unaffected, only AROVA will failover to the secondary region and the production VMs will continue running fully protected in the primary region. Conversely, if production VMs are impacted by a failure while AROVA remains unaffected, the primary region AROVA can initiate failover of the affected production VMs to the secondary region. In the event of a disaster affecting multiple Protected Domains, the user will have to define the failover order and concurrency for each Domain.

Follow the links below to learn more about failover.

See:

Performing Failover

VM Properties Compatibility on Failover

Test Failover