Fourth article about VAO 3.0 and the second use case.
How to use a Backup Job to implement a DR scenario with VAO. In this article, I don’t cover the mandatory step related to VMs tag.
The main steps are:
- Creating a Failover location where the VMs can be restarted
- Setting up scope
- Creating the orchestration plan
1 . Creating the Failover location
Pictures 1 to 3 show how easier it is to set Name, computers, and storage resources.
Picture 4 shows the maximum storage % that can be used by Restore task and picture 5 shows if the Instant VM recovery has to be enabled.
Picture 6 shows one of my favorites VAO options.
Why? Because it allows VAO to be implemented where the primary backup job has been copied to a second location.
To be clearer: the VBR backup copy job allows to copy backup data to the secondary site. If there are VMware hosts, it’s possible to create a DR site just restoring data from backup copy job.
Picture 7 shows how to twin the production with DR networks (the previous step sets-up the re-IP addressing just for windows VMs)
Picture 8 shows the GDPR option
2. Setting up scope
Pictures 9 to 12 show the main points:
To set-up a scope, check-up the VM Groups, select the Recovery Location and which plan steps have to be added. (all details are available at Baseline articles).
3. Creating the Orchestration Plan
From Picture 13 to 16 the main points to set up the Restore Plan
Please find here an example of Readiness check Reports