Veeam: Backup and restore workloads to Microsoft Azure – Migrate workloads from Microsoft Azure to our Datacenter

Greetings friends, I continue with this very interesting series about Veeam and Microsoft Azure, we have already seen practically all the steps: from interconnecting Microsoft Azure with our Datacenter, deploying the VBR in Azure, launching the copy job jobs, and of course restoring Microsoft Azure, today I bring you how to bring those VM in Azure back to our Datacenter, as you can see in this illustration:

Veeam: Backup and restore workloads to Microsoft Azure – Configuration in our Datacenter for backup to Microsoft Azure

Greetings, I continue with the series on Veeam and Microsoft Azure, let's remember the diagram of the introduction where we presented the workflow. What I'm going to show you today, step by step, is the configuration in our Veeam Backup & Replication Server of our datacenter.

Adding the Microsoft Azure repository in our Data Center

The first step of this blog, is to add the Microsoft Azure repository, in our local datacenter, remember that we have configured a new VBR in Microsoft Azure, and that we have inter-connected our datacenter and Azure. We will go to Backup Repositories - Add Repository

Veeam: Backup and restore workloads to Microsoft Azure – Deploy Veeam Backup & Replication in Microsoft Azure

Greetings friends, I continue with the series about Veeam and Microsoft Azure, if we remember the drawing of the first entry, we will see that in Microsoft Azure we will deploy a Veeam Backup & Replication server, with the purpose of serving as a Backup Repository, and at the same time be able to operate and recover jobs directly to Azure, in case our main datacenter fails:

Deploying Veeam Backup & Replication directly from the Azure Marketplace

Veeam has been offering Veeam Backup & Replication 9.5 U3 directly from the Azure Marketplace for some time now, this is very convenient and includes:
  • A fully functional and installed Windows Server 2016.
  • An automatically pre-installed instance of Veeam Backup & Replication 9.5U3, with SQLexpress
From our Microsoft Azure console, click on Create a resource, and search for Veeam, we will see several results, in this case select Veeam Backup & Replication 9.5

Veeam: Backup and restore workloads to Microsoft Azure – Connectivity between our Datacenter and Microsoft Azure

Greetings friends, if we remember the introduction to this series on how to create a Disaster Recovery plan with Veeam in Microsoft Azure, we had the following diagram: In the diagram we can see how between the two locations we are using Veeam PN for connectivity, in this article today we will see the step-by-step steps to deploy and configure VeeamPN in both locations.

Deploy Veeam PN Network Hub to Microsoft Azure

Veeam Powered Network can be deployed directly from the Microsoft Azure Marketplace, making it very simple and convenient to use. From the Microsoft Azure console, we will go to Create a resource and search for Veeam, among the results we can see Veeam PN for Microsoft Azure, we will select it:

Veeam: Backup and restore workloads to Microsoft Azure – Introduction

Greetings friends, every day it is more common to move workloads to Microsoft Azure, or at least to have planned a certain level of Disaster Recovery to Microsoft Azure in case of a complete shutdown of our main data center, to be able to restore those most urgent applications for users or customers, reducing service downtime. Veeam has a number of specific products for moving workloads to Microsoft Azure, easily and fully integrated into the Veeam Backup & Replication console itself. The main functionality, available since March 2016, is called Direct Restore to Microsoft Azure, and although it used to come as a separate application it is now available on the Veeam Backup & Replication console itself to help with its integration.

Infrastructure topology

I would like to show you this diagram (thanks to Allan Hammond for his help with the diagram) so that we can understand Veeam's workflow between the local data center and Microsoft Azure and vice versa: