Before failing back protected VMs, AROVA must be deployed to the secondary region. After deployment, the script can call the AROVA to start AROVA Configuration Disk ("ACD") backward replication.

    • In the case of an actual failure of the primary region, ACD backward replication within the same zone will fail. However, this is a viable option if it is desired to deploy AROVA gracefully to the secondary region (when no error condition exists). Review information about persistent disk storage scopes.

Note: In the case of an actual primary region failure, ACD backward replication should be triggered after the primary region has been recovered.

Follow these steps to deploy the ACD:

    • From the AROVA UI, navigate to the Configurations screen and click the Configure Config Disk link.


Figure: Configuring the AROVA Configuration Disk.

    • Specify the desired configuration zones.
    • Click the Configure button to initiate backward replication.

Figure: Configure and start backward replication of the Config Disk.

    • Progress of the replication task to create secondary disks for the ACD can be viewed from the Task Log.
    • After initial replication of the ACD is complete, the secondary region AROVA can be shut down and a new AROVA can be deployed for recovery to the primary region.


Note: In case of partial or full zonal failure, the primary region AROVA will continue running and it is not necessary to perform the above steps to redeploy the ACD to the primary region.

Also see:

View: Failback

View: Failback Protected VMs

View: Cleaning the Primary Region