Veeam CDP – Manual Upgrade

Nel mio laboratorio, il sito di Disaster Recovery è composto da un singolo host ESX 7.01.

Viene gestisto da un vCenter virtuale (denominato vCenter-DR), che afferisce esclusivamente alle risorse hardware messe a disposizione dallo stesso host ESX 7.01.

Lo scorso mese Veeam Software ha rilasciato l’aggiornamento di Veeam Backup & Replication 11A.

Tra le diverse migliorie introdotte, la mia attenzione si è concentrata sui nuovi driver (detti I/O filters) della componente CDP.

Se nel cluster principale, l’aggiornamento è stato semplice, immediato e indolore (vista la presenza di più host sotto un ulteriore vCenter), per il sito di Disaster Recovery si è generata una complicanza collegata all’architettura hardware presente.

L’aggiornamento falliva, poichè era impossibile porre l’host ESX 7.01 in mantenance mode senza di fatto spegnere anche il vCenter-DR che lo gestiva (vedi immagine 1).

Immagine 1

Come è stato possibile superare tale ostacolo senza modificare la configurazione del cluster? (Senza cioè aggiungere un ulteriore Host ESX 7.01)

La procedura che ho seguito è stata semplice e sfrutta la kb 2008939 di Vmware (

Costa di due fasi principali:

  1. Copia del pacchetto Veeam CDP nell’host ESX 7.01 (
  2. Installazione del pacchetto attraverso il  comando “esxcli software vib update -d /yourpath/” (vedi Immagine 2)

Immagine 2

Terminata questa prima fase, è ora stato sufficiente ripetere la procedura standard di aggiornamento (vedi immagini 3,4 e 5).

Immagine 3


Immagine 4


Immagine 5

La verifica che garantisce che la procedura seguita è corretta è quella di realizzare un Job di Replica CDP, attendere che si concluda senza errori e che  sia possibile avviare la procedura di failover.

Nota 1: La procedura di aggiornamento dei I/O filters è disponibile nel manuale alla seguente pagina:     (

Nota 2: Prima di procedere è obbligatorio confrontarvi con il supporto Veeam attraverso l’apertura di un tiket (

A presto

VDrO v.4 – Run a DR plan

This is the last article about how to integrate the Continuous Data Protection (CDP)  technology (available from VBR v.11) and VDrO v.4 (former VAO).

In this part, we are going to see what happens when an orchestration plan is launched.

Yes, I wrote the word “see” because I created a short video showing the tasks that are automatically completed when a Disaster Recovery is occurring.

If you need more details about how to set up the environment, please read the previous articles.

Let me know if videos and youtube platform are a good way to expose technological valuable topics.

Thx for reading and watching and take care

VDrO v.4 – Create a DR plan

C. Create an Orchestration Plan

The DR plan is a sum of more Orchestration plans. This article is going to explain how to create them.

Just a small and important note before continuing: it’s mandatory to have already completed the steps described in the last article.

Let’s start!

From the main menu of the VAO server select the Manage button.

Now click on New as shown in picture 1.

Picture 1

The easy wizard is going to ask to choose a scope.

In our example, we use Linux-CDP as shown in picture 2.

Picture 2

Now fill up the plan info with the Plan Name, the description, the contact name of the plan (picture 3),

Picture 3

Select the type of Plans. In this article choose the CDP replica (picture 4)

Picture 4

In the next step please check if the correct “VM Group” appears.
If it doesn’t, it’s necessary to go back to the setup phase (please read the previous article) and fix the issue.

In our example, it appears correctly (Ubuntu-CDP) as shown in the next two pictures (5 and 6).

Picture 5

Picture 6

The next step shows the VM Recovery options (picture 7).

It gives the operator control of the plan. For example, stopping the plan if something goes wrong.

Picture 7

In “New VM Template” menu the VAO user can add additional steps to the orchestration process; for example, starting the CDP replica job first and shut down the source VM after (Picture 8)

Picture 8

Tips I: I created a customized script to change the IP Address of the VM.

Tips II: it’s possible to set up the access credential directly from this page by clicking the button on the bottom of the page. It is available for Windows VM only.

The next step defines the RTO & RPO.

The most important thing to remember here is that the RPO has to be equal or major than the RPO set in the CDP replica job (picture 9). 9

The last steps define when the plan report shall be automatically generated (picture 10) and if the readiness check has to run at the end of every single wizard (recommended option) (picture 11).

Picture 10

Picture 11

The result is shown in picture 12

Picture 12

The next article is going to be a video to see VDrO in action.

Take care and see you soon

VDrO v.4 – Setup a Plan from CDP Replica

In this article, I’m going to show you how to set up an orchestration plan using as a source a CDP replica Job.

This article will not cover how to create and run a CDP replica job from VBR console. If you need a guide please refer to the official guide.

There are four main parts:

  1. Create a Business Category
  2. Setup the Environment
  3. Create an Orchestration Plan
  4. Launch the Orchestration Plan

The first and the second topics will be described in this article. The third and the fourth ones in the next articles.

A. To create a business category for CDP replica, just open the Veeam ONE interface from the VAO server (picture 1).

In this example, the business category is called Ubuntu-CDP , the resource group is called CDP-Linux (Picture 2).

Picture 1

Picture 2

B. After opening the VAO web interface it’s necessary to follow the next four steps.

1. Add a Role and Scope (picture 3).

In my example, the scope is named Linux-CDP.

The plan Author/Operator is VBR.

Picture 3

2. Add or modify the Recovery Location (picture 4).

In my example, the recovery location is Verderio and has the Cluster-Verderio as Compute resource (Picture 5).

Pictures 6 and 7 show how to remap the Networking and how to set up the changing IP address rules.

Picture 4

Picture 5

Picture 6

Picture 7

Note1: The Re-IP feature is available just for Windows VMs (please have a look at the official documentation to get all detail (user guide). For Linux VMs it’s necessary creating a custom script.

3. Reporting

Pictures 8, 9, and 10 show how to assign the Linux-CDP scope to your custom reports.

Picture 8

Picture 9

Picture 10

4. Assign the plan Components

Picture 11

Picture 12 shows how to add the VM group called Ubuntu-CDP to the scope Linux-CDP.

Picture 12

Picture 13 shows how to add a recovery location, i.e. Verderio.

Picture 13

Picture 14 shows how to add the plan steps to the orchestration plan (In my example I included all the plan steps).

Picture 14

The next article shows how to create an Orchestration Plan and run it.

Suggestion: If you can’t wait and want to do it immediately, just read the previous articles 🙂

See you soon and take care.