Failback is the process of returning workloads from the secondary region back to the primary region once it is healthy and available again. Failback is fully orchestrated by AROVA and can be run from either the primary or secondary site.

Note: The Protected Domain is the fundamental unit of failback. All protected VMs of a Domain will be failed back together as part of the same failback task.

    • Identical failback steps are applicable to all Protected Domains unrelated to the Domain’s VM protection scope (zonal or regional) and initial failure nature (partial, full zonal, or regional). VM disk scopes (zonal or regional) are preserved on failback.
    • AROVA can manage failback from either region. AROVA may be allowed to remain at the secondary site; however, it is recommended to ultimately relocate AROVA back to the primary site when possible.
      • AROVA can be returned to the primary site (failback) any time after AROVA Configuration Disk (ACD) replication has been completed.
    • The following diagram illustrates the secondary and primary regions of AROVA managed disk state machines:

Figure 111: AROVA managed disk state machines.

Follow the links below to learn more about failback.

See:

Cleaning the Primary Region

AROVA Failback

VM Failback