AROVA orchestrates the failback of VMs. If a valid, current copy of AROVA is not available, it must be re-deployed before failback can be performed. AROVA can be run from either the primary or secondary site; however, it is recommended to move AROVA back to the primary site in most situations.

    • AROVA can be failed back to the primary region after the secondary region AROVA has completed ACD replication.
      • The secondary region AROVA can then be deleted and a new one deployed (in recovery mode), if necessary.

Note: In the case of partial or full zonal failure, the primary region AROVA will continue running uninterrupted. In this situation, it is not necessary to re-deploy AROVA.