VDrO-Baseline 1

August’s 2022 topic is VDrO (former VAO)

This topic needs an awfully long time to be rightly covered. For this reason, I wrote 5 articles.

The first two will explain the base concepts in front of technology. The others will cover how to set up VDrO for managing the Veeam Replica job, the Veeam Backup job, and the Netapp Storage Replica.

Here below all the direct links to the topic:

Baseline-2VBR-ReplicasVeeam BackupNetapp integration

In these articles, I will not manage how to install VDO software; please refer to the deployment guide (VDrO Guides).

  1. VDrO – Baseline-1:

One of the common requirements of big companies is to automatically manage Disaster Recovery.

Let’s see the decisional process of the IT Manager

These are the VDrO answers.

Let’s move to the VDrO console:

The first steps after logging in (picture 1) is to click on the administrator tab (Yellow on picture 2) and check the license file installed (picture  3)

Picture 1

Picture 2

https://lnx.gable.it/wp-content/uploads/2020/07/VAO-login.jpgPicture 3

Now I’m going to describe the structure of the software components.

VDrO Server:  it shows where the VDrO Server has been installed (Picture 4)

Picture 4

The VDrO architecture is well-represented in picture 5 where three production sites replicate their data to a DR site.

Picture 5

Is it important to fill up the VDrO Server form? Yes, because VDrO creates automatically the DR- Plan documentation.

In my lab, I have just a production site and a  DR site.

VDrO AGENTS: to control the activities of the Backup Server located in production sites, VDrO installs his own agent. The installation task is performed directly from the VDrO console (Picture 6).

Picture 6

vCENTER SERVERS: in my scenario, there are two vCenters; the first one in production and the second in DR site (Picture 7).

(Picture 7)

STORAGE SYSTEM: the most important VDrO news is the integration with storage replication technology. This version supports just Netapp. Picture 8 shows how to add the Storages to VDrO.

Picture 8

The last VDrO article will deal with how to set up and use this great technology.

RECOVERY LOCATION: it’s the place where the DR will be performed (Picture 9). It can be different locations in respect to where VDrO is installed.

Picture 9

In the next rows and pictures, I’ll show which info VDrO needs to work at its best.

In particular, I’m talking about the resources present in the recovery location. In this example the computer resources (Picture 10) and storage resources (picture 11).

Picture 10

Picture 11

The next 10 rows are very important to fix in mind.

How the VDrO can understand which resources are available? In other words, how can I assign resources to my Failover Plan?

The answer is VDrO uses massively tagging to all resources present at the VMware level.

Tagging means that resources can be added to VDRO

But …. is it possible to tag the resources?

Yes, It’s possible because inside VDrO there is the Veeam ONE Business-View component that can be freely used to tag resources.

To have more details about tagging please refer to the VDrO-guide.

One of the most common requests from the customers is to create automatic documentation about failover for both testing and procedures.

VDrO has already templates (in different languages that you can personalize at will) that are automatically filled up from software when you test or perform the Disaster Recovery.

In the next two pictures, it is shown how to set up an e-mail subscription (Picture 12) and configure the report Detail level (Picture 13).

Just remember to subscribe to the report to the right scope.

(Picture 12)

(Picture 13)

The next option is the reason why I fell in love with VDrO (Picture 14).

(Picture 14)

As you can see there is a big choice with DR plan steps. What does it mean?

Let’s see it with an easy example:

My DR plan requires switching on the Domain Controller (VM1) and afterward the SQL Application (VM2).

I want also to be sure that

a. the original VMs are switched off before starting the DR plan

b.  when DR-plan is up and running, the SQL application has to answer port 1433.

What the VDrO can do for you?

With the pre-plan step, you can check the original VMs are switched off.

With a post-plan, you can check that the application answers correctly.

Another great point about plan steps is that you can choose if the actions have to be executed or skipped. In this way, it adds more flexibility to the solution.

(Picture 15)

Picture 16

It’s time to have a break. My next Article (VDrO – Baseline 2) will show scopes and plan components.

VDrO-Baseline 2

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

Picture 1

The VDrO 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 VRrO 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 it 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

The 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

Pictures 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!