Veeam Disaster Recovery Orchestator v.4 – How to Upgrade

Also Veeam Availability Orchestrator, commonly called VAO, changed its name with this new release.

The new name is Veeam Disaster Recovery Orchestrator (VDrO).

The main news of this version is the support of the technology of continuous data protection (CDP) introduced in VBR v.11.

Which are the main benefits allowed by this new feature?

  • New readiness checks now including RPO and SLA.
  • Recovery Point Object close to real-time.
  • Detailed reports to track and audit the Disaster Recovery plan of your company.

The next article will explain how to implement a DR plan using CDP.

Before doing the upgrade procedure please:

  1.  Perform backup of all existing databases (VAO, VBR, ONE)
  2. Make sure there is enough space for the upgrade of the Microsoft SQL Server configuration database
  3. Make sure there are no orchestration plans being tested or executed
  4. Make sure there are no orchestration plans scheduled to run during the upgrade.
  5. Read carefully the user guide.

Before proceeding please check that the VAO current version on the server is 3.0 (picture 1).

Picture 1

After downloading the ISO file from the Veeam website and mounting it (picture 2)

Picture 2

just select the “Setup” voice; the wizard immediately begins the upgrade (picture 3).

Picture 3

Please check that the previous version of VAO has been discovered. If so the upgrade button is available (picture 4).

Picture 4

The setup checks if Visual C++ 2019 Redistributable package is already installed.  If not it will automatically be deployed. This procedure requires the server reboot (pictures 5 and 6).

Picture 5

Picture 6

After reboot is completed, relaunch the setup.  The wizard will show which components will be automatically upgraded (picture 7).

picture 7

Now the wizard will ask for a valid license (picture 8) and will install the missing components (Pictures 9 and 10).

Picture 8

picture 9

picture 10

The next steps are about the Veeam Databases.
The wizard will ask to connect to them and update the VBR one if necessary (pictures 11 and 12).

Picture 11

Picture 12

The main point of the upgrade procedure is the certification step.
As shown in picture 13, the wizard will ask the VAO administrator which certificate to use. It can be a self-signed and autogenerated or an own certificate created from an external authority.
My suggestion is to ask your security specialist to know which is the best choice for your company.

Picture 13

Picture 14

Clicking on the install button it will complete the upgrade wizard as shown in pictures 15 & 16.

Picture 15

Picture 16

After upgrading please check the versions of VAO (4.0.0.2088), VBR (11.0.0.837), ONE (11.0.0.1379) now installed.

Just a note before ending the article: has already said, VAO (Veeam Availability Orchestrator) has changed its name to VDrO  (Veeam Disaster Recovery Orchestrator).
The web pages of the product still show the old name. It will be updated in the next release.

That’s all for now guys. Take care

Digital Trasformation & Data Mobility

If Cloud has been the most used word in the last five years, the words that have been buzzing the IT world in the last five months are Digital Transformation

From Wikipedia:

Digital Transformation (DT or DX) is the adoption of digital technology to transform services and businesses, through replacing non-digital or manual processes with digital processes or replacing older digital technology with newer digital technology”.

Or: Digital Transformation must help companies to be more competitive through the fast deployment of new services always aligned with business needs.

Note 1: Digital transformation is the basket, technologies to be used are the apples, services are the means of transport, shops are clients/customers.

1. Can all the already existing architectures work for Digital Transformation?

  • I prefer to answer rebuilding the question with more appropriate words:

2. Does Digital transformation require that data, applications, and services move from and to different architectures?

  • Yes, this is a must and It is called Data Mobility

Note 2: Data mobility regards the innovative technologies able to move data and services among different architectures, wherever they are located.

3. Does Data-Mobility mean that the services can be independent of the below Infrastructure?

  • Actually, it is not completely true; it means that, despite nowadays there is not a standard language allowing different architecture/infrastructure to talk to each other, the Data-mobility is able to get over this limitation.

4. Is it independent from any vendors?

  • When a standard is released all vendors want to implement it asap because they are sure that these features will improve their revenue. Currently, this standard doesn’t still exist.

    Note 3: I think the reason is that there are so many objects to count, analyze, and develop that the economical effort to do it is at the moment not justified

    5. Is already there a Ready technology “Data-Mobility”?

    The answer could be quite long but, to do short a long story, I wrote the following article that is composed of two main parts:

  • Application Layer (Container – Kubernetes)
  • Data Layer (Backup, Replica)

Application Layer – Container – Kubernetes

Using Local Persistent Volumes with Container Engine for Kubernetes | IaaS Blog - Oracle Cloud Infrastructure News

In the modern world, services are running in a virtual environment (VMware, Hyper-V, KVM, etc).

There are still old services that run on legacy architecture (Mainframe, AS400 ….), (old doesn’t mean that they are not updated but just they have a very long story)

In the next years, the services will be run in a special “area” called “container“.

The container runs on Operating System and can be hosted in a virtual/physical/Cloud architecture.

Why containers and skills on them are so required?

There are many reasons and I’m listing them in the next rows.

  1. The need of IT Managers is to move data among architectures in order to improve resilience and lower costs.
  2. The Container technology simplifies the developer code writing because it has a standard widely used language.
  3. The services ran on the container are fast to develop, update and change.
  4. The container is de facto a new standard that has a great advantage. It gets over the obstacle of missing standards among architectures (private, hybrid, and public Cloud).

A deep dive about point d.

Any company has its own core business and in the majority of cases, it needs IT technology.

Any size of the company?
Yes, just think about your personal use of the mobile phone, maybe to book a table at the restaurant or buying a ticket for a movie. I’m also quite sure it will help us get over the Covid threat.

This is the reason why I’m still thinking that IT is not a “cost” but a way to get more business and money improving efficiency in any company.

Are there specif features to allow the data-mobility in the Kubernetes environment?

Yes and for giving you a great example please have a look at the Kasten K10 product because it has many and advanced features (The topic will be well covered in the next articles because it is one of my great working passions).

Data-LayerCloud Backup Restore Icona - Download gratuito, PNG e vettoriale

What about services that can’t be containerized?

Is there a simple way to move data among different architectures?

Yes, that’s possible using copies of the data of VMs, Physical Servers.

In this business scenario, it’s important that the software can create Backup/Replicas wherever the workloads are located.

Is it enough?

From my point of view, it is not. The software has to be able to restore data intra-architectures.

For example, a customer can need to restore some on-premises workloads of his VMware architecture in a public cloud,  or restore a backup of a VM located in a public cloud to a Hyper-V on-premises environment.

In other words, working with Backup/Replica and restore in a multi-cloud environment.

The next pictures show the Data Process.

I called it “The cycle of Data” because leveraging from a copy it is possible to freely move data from and to any Infrastructure (Public, hybrid, private Cloud).

Pictures 1 and 2 are just examples of the data-mobility concept. They can be modified by adding more platforms.

The starting point of Picture 1 is a backup on-premises that can be restored on-premises and on-cloud. Picture 2 shows backup of a public cloud workload restored on cloud or on-premises.

It’s an open circle where data can be moved around platforms.

Note 4: A good suggestion is to use data-mobility architecture to set up a cold disaster recovery site (cold because data used to restore site are backup).

Picture 1

Picture 2

There is one more point to complete this article and it is the Replica feature.

Note 5: For Replica I intend the way to create a mirror of the production workload. Comparing to backup, in this scenario the workload can be switched-on without any restore operation because it is already written in the language of the host-hypervisor.

The main scope of replica technology is to create a hot Disaster Recovery site.

More details about how to orchestrate DR are available on this site at the voice Veeam Availability Orchestrator (Now Veeam Disaster Recovery Orchestrator)

The replica can be developed with three different technologies: 

  • Lun/Storage replication
  • I/O split
  • Snapshot based

I’m going to cover those scenarios and kasten k10 business cases in future articles.

That’s all for today folks.

See you soon, and take care.

Stella – Il mio cane

Oggi 26 Febbraio 2021 Stella ci ha lasciato.

Era qualche mese che stavi orgogliosamente lottando e noi con te.

Mi mancheranno i nostri “Buongiorno Stellina”, qualche carezza e poi subito a fare colazione, dove con i tuoi dolci occhi chiedevi un biscotto ben inzuppato nel Capuccino.

Poi mi seguivi fino all’auto come se dovessi essere il mio accompagnatore della giornata.

A fine giornata aprivo il cancello e tu eri li ad aspettarmi,  annussavi l’auto per determinare quali strade e persone avessi incontrato.

Ricordi di noi insieme ne ho tantissimi.

Da quello più tenero legato alle serate sdraiati sul divano a guardare dei film dove era impossibile arrivare alla scritta “The End”  perchè richiedevi quelle attenzioni che non avevi ricevuto di giorno.

A quello più gioioso dove correvi per il giardino e per campi alla ricerca di profumi nuovi anche se conoscevi perfettamente il territorio.

Oppure ancora quando ti buttavi nell’acqua del lago per rinfrescarti da una lunga corsa.

Tu riuscivi ad accendere le giornate uggiose per il clima e tristi per l’animo.

Grazie di essere stata il mio cane

Ciao Stellina