Cleaning the Primary Region
After the primary region has been recovered from a failure it may still contain stale production VMs and an old AROVA.
- The stale production VMs must be removed from the primary region before initiating failback.
- If VMs with the same name are present in the target zone of the primary region, AROVA will not allow the failback operation to proceed.
- Any stale instances of AROVA must also be cleaned up.
- After the primary region is recovered, it is recommended to re-deploy a new AROVA to it.
- If a stale instance of AROVA exists in the primary region, the AROVA deployment script will fail and display a warning message.
- The script can be restarted using the same arguments after the stale AROVA has been deleted.
- AROVA can failback to the primary region after the secondary region AROVA completes its ACD replication.
- The secondary region AROVA can then be deleted and a new one deployed (in recovery mode), if desired.
Also see: