In today example, I imagined implementing a DR-Orchestration for a company selling tickets. The two VMs that deliver the services are the Domain controller and SQL DB with installed the application needed.
The main points are:
Setting up replica job using VBR present into VAO (VBR-VAO)
Adding the plan components to the scope
Creating a lab group
Configuring the Orchestration Plan
1. Setting up Replica Job
From the Veeam console, it’s quite easy to set up the Replica Job (From Picture 1 to 5)
Veeam-One Business View is reachable from the Veeam Monitor console. To create the tagging just select add Category (Picture 7) from the resource you want to tag (in the picture are Virtual machines).
After folding it up with a name (Picture 8) in pictures 9, 10, 11, and 12 is shown how easy it is customizing the tag.
Picture 11 shows how to concatenate the conditions.
thIt means that it is possible to add different conditions selecting for every entry the logical operator “and – or”
3. Adding the plan components to the scope
From the Administrator panel, through plan components, it is possible to select which VM groups can be added to the scope.
In our example, we are going to create a DR-strategy for SQL-Production scope (picture 14) using the VM Groups named SQL – Produzione (Picture 15). How to do it? Just clicking on the include button.
Now it’s time to repeat the same procedure for Recovery location (Picture 16), Plan steps (Picture 17), Credential (Picture 18), and Template jobs (Picture 19).
Now that we have finally added all componentsto the baskets. weneed to create an Orchestration Plan for this specific service.
4. Creating a Lab group
From the main menu select Datalabs entry.
Now clicking on the add button, it’s possible to assign the tasks that will be performed during tests to the Datalab as shown in Picture 20,21,22.
Remember that the Datalab assignment has been already performed from the VAO administrator page.
Let’s continue the VAO features description talking about scope (Picture 1)
VAO controls access to its functionality with the scopes.
A scope defines which operations users can perform.
Let’s back to my example, I created a SQL Production scope where only the users belonging to the SQL administrator group can manage and launch the DR process.
The plan components are probably the main VAO attention point (Picture 2).
From this menu, it’s possible to group as a single entity all objects you need to create a Disaster Recovery strategy.
I’m talking scope (first to select), VM (applications and services), recovery locations, plan steps, credentials, and jobs template.
To be clearer, it’s like creating a picnic basket and putting inside different dishes.
Now you just have to lay the table.
How to do it? (Which dishes do I have to put into the basket?)
Just select scope (Picture 4), then from VM groups include the needed VMs source (Picture 5), from recovery locations select the DR site (picture 6) and at the end select plan steps, credential and Template Job.
Last point is the DataLabs assignment but I’m sure you can now include them on the right scopes.
Exit from the Administrator menu and move to the main menu to create the first Recovery Plan.
The wizard is very easy to be used:
Picture 8 shows how to select the Scope.
Picture 9 shows the detailed plan info and Picture 10 the plan type (next articles will deep how to set them up)
Picture 11, 12, 13 show how it’s possibles to discover the VMs that belong to the groupselecting VM group
Picture 14 shows the control options for the DR plan. If something goes wrong the plan can be halted or not.
Picture 15 shows the steps, 16 the option to protect VMs switched on after the failover has been completed, 17 the RPO and RTO that the plan has to respect.
Picture 18 shows the template docs that will be used, while picture 19 shows a (for me)interesting mandatory check option.
Before doing any new activity the Readiness check analyzes that all components are correctly set up.
In my next article, I will cover two examples: DR-plan from Replica and DR-plan from backup. Keep in touch!