Veeam Availability Orchestrator – v.3.0 – DR from Backup

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.

If you need a guide please refer to my previous writes (Baseline  1  & 2)

The main steps are:

  1. Creating a Failover location where the VMs can be restarted
  2. Setting up scope
  3. Creating the orchestration plan

Let’s start!

1 . Creating the Failover location

Pictures 1 to 3 show how easier it is to set Name, computers, and storage resources.

Picture 1

Picture 2

Picture 3

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 4

Picture 5

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 6

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 7

Picture 8 shows the GDPR option

Picture 8

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).

Picture 9

Picture 10

Picture 11

Picture 12

3. Creating the Orchestration Plan

From Picture 13 to 16 the main points to set up the Restore Plan

Picture 13

Picture 14

Picture 15

Picture 16

Please find here an example of Readiness check Reports

Readiness check report example dowload

Veeam Availability Orchestrator – v.3.0 – DR from Replicas

First step by step guide how to set-up a Disaster Recovery plan starting from a replica job.

Anyway I suggest having a look at the previous articles befere reading this one.

Veeam Availability Orchestrator – v.3.0 – VAO-Baseline-1

Veeam Availability Orchestrator – v.3.0 – VAO-Baseline-2

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:

  1. Setting up replica job using  VBR present into VAO (VBR-VAO)
  2. Creating Tags
  3. Adding the plan components to the scope
  4. Creating a lab group
  5. Configuring the Orchestration Plan
  6. Testing

1.  Setting up Replica Job

From the Veeam console, it’s quite easy to set up the Replica Job (From Picture 1 to 5)

Picture 1

Picture 2

Picture 3

Picture 4

Picture 5

Picture 6

 

2.Creating Tags

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).

Picture 7

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 8

Picture 9

Picture 10

Picture 11

https://lnx.gable.it/wp-content/uploads/2020/08/bw-5.jpgPicture 12

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.

Picture 13

Picture 14

Picture 15

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).

Picture 16

Picture 17

Picture 18

Picture 19

Now that we have finally added all components to the baskets. we need 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.

Picture 20

Picture 21

Picture 22

5. Configuring the Orchestration Plan

The configuration wizard has been already explained in my previous article (VAO 3.0 – Baseline2).

Please find hereafter a short summary.

If you set it up correctly you should see your VMs in the VMGroups (picture 27&28) as they belong to the scope set on step 2 (Picture 24)

Picture 23

Picture 24

Picture 25

Picture 26

Picture 27

Picture 28

Picture 29

6. Testing

There are two different tests performed by VAO 3.0

Readiness Check (Picture 30-31) is a low-impact method to confirm that the configuration of an orchestration plan matches the DR environment.

Datalab Test simulates the DR starting VMs, Applications and Services into a different network. The data labs have to be set-up from the VBR console (Picture 32-34).

Picture 30

Picture 31

Picture 32

Picture 33

Picture 34

All reports are available from Reports menu (Picture 35)

Picture 35

Please find here two examples

– Readiness check report example download

– Datalab Test example download

The next articles will talk about Backup and Replica Storage.

Veeam Availability Orchestrator – v.3.0 – VAO-Baseline-2

Let’s continue the VAO features description talking about scope (Picture 1)

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).

(Picture3)

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.

Picture 4

Picture 5

Picture 6

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 7

Picture 8 shows how to select the Scope.

Picture 8

Picture 9 shows the detailed plan info and Picture 10 the plan type (next articles will deep how to set them up)

Picture 9

Picture 10

Picture 11, 12, 13 show how it’s possibles to discover the VMs that belong to the group selecting VM group

Picture 11

Picture 12

Picture 13

Picture 14 shows the control options for the DR plan. If something goes wrong the plan can be halted or not.

Picture 14

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 15

Picture 16

Picture 17

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.

Picture 18

Picture 19

In my next article, I will cover two examples: DR-plan from Replica and DR-plan from backup. Keep in touch!