#Veeam backup to azure install#

In my Virtual Network, there is only the default.ДЇinally, Click Apply and watch the proxy get deployed to the Azure account. If you have multiple subnets, the selection is here as well. Last is the selection of the Virtual Network, pre-provisioned in Azure, from the drop down list. Then, enter in a unique name for DNS, in my example, .com. Resource groups are a a must in Azure to group resources together, and the Veeam Proxy can be deployed into an existing group, or provisioned inside a newly defined Resource Group. Resource Group is the next choice to make. This is also where we select which Storage account to deploy into, which was part of the pre-requisites.

In my example, I chose Basic_A2, which is 2 cores, and 3.5GB of memory. On the next screen, we can select the Azure size for the VM. Choose the Azure subscription that was previously entered, and choose the region in which you have a storage account, and network pre-provisioned. Also note, that all traffic will traverse a single port from the on-premises location to Azure: 6181.ДЇor deployment model, select the default Azure Resource Manager, and click next. The first screen is simply entering a name for the new proxy.ДЄfter clicking next, add in credentials that will act as the local administrator account for the newly deployed Azure Proxy. In the Veeam Backup and Replication console, choose to Deploy Azure Proxy from the Proxy location, under Backup Infrastructure. With those out of the way, itвЂ™s time to open the deployment wizard.

#Veeam backup to azure install#

Add in a new set of credentials, and install the Azure powershellВ module as directed, if not already installed. The best part? The Azure proxy is only powered on when needed! Ready, Set, Deploy!Д«efore we open the deployment wizard, we have 2 prerequisites:ДЄzure credentials will need to be added into the VBR console, by selecting the Menu icon in the upper left, and choosing Manage Azure Accounts. Once the proxy is deployed to Azure, traffic will now flow from backup file, to source proxy, to Azure proxy, to the newly created Azure VM, with data staying deduped and compressed during its travel on the WAN between proxies.

But, by provisioning a Veeam proxy server in Azure ahead of time, we can greatly speed up the restore process. This may not be the prefered path, especially if you donвЂ™t have the best bandwidth. So, in this small series, we are going to look at using Veeam to restore your Hyper-V or VMware virtual machine up into Azure.ДЇirst things first, Veeam can restore any virtual machine that it backed up directly to MicrosoftвЂ™s Azure by simply entering your Azure credentials, and selecting some options.

There are many reasons to run virtual machines in the public cloud, and more and more companies are taking advantage of the flexibilityВ and scalability that it offers.