Veeam Direct Restore to Microsoft Azure: How to Deploy the Azure Proxy Server?

Veeam Direct Restore to Microsoft Azure: How to Deploy the Azure Proxy Server?Within the Veeam Backup & Replication console you’re able to now directly recover VMs of any Veeam type including, VMware, Hyper-V, Physical or Endpoint directly out to your Microsoft Azure environment. In my previous post, How to Setup Veeam Direct Restore to Microsoft Azure, I detailed all of the steps required to make Veeam Backup & Replication 9.5 aware of your Azure Subscription. This process is required before moving forward with the restore process which we’ll begin to dive into here.

Veeam: Direct Restore to Microsoft Azure in the UIVeeam 9.5 Direct Restore to Microsoft Azure within the Backup & Replication UI

There are many variables that can play into the actual Recovery Time Objective whenever you’re recovering data out over a Wide Area Network (WAN) connection. The largest variable there being the network connection. Veeam customers are already familiar with the concepts of the Backup Proxy. In distributed environments where data is being sent over a WAN connection from one data center to another it is a best practice to deploy at least one backup proxy server in the source site as well as at least one backup proxy server in the target site.

Veeam: Distributed Architecture

The scenario of restoring physical and virtual machines from backups residing in the on-premises environment to Microsoft Azure is very similar. The purpose of the Backup Proxy servers on-premises and in Azure is to compress and deduplicate the data. This will help to reduce the amount of network traffic and then in turn increase the speed of the restoration process. In your Azure environment if you utilize multiple Azure data centers – for instance US East, US West and Australia East, you should deploy an Azure Proxy Server in each data center.

The process of deploying an Azure Proxy server is completely automated and very simple to complete. Lets take a look at the steps and dive in a bit deeper!

Steps to Deploy a Veeam Azure Proxy Server

The Azure Proxy server is deployed as a pre-configured Microsoft Windows Server 2012 R2 virtual machine within Azure that is left powered off until the restore process is initiated on-premises.

Within Backup & Replication navigate to the Backup Infrastructure tab and right click on Backup Proxies – Choose Add Azure Proxy.Veeam: Deploying an Azure Proxy Server

Give the Proxy Server a meaningful name. I like to include the Azure Data center in my proxy server names. Just note that you cannot have any special characters in the proxy server name.

Veeam: Add Azure Proxy

Next you’ll need to specify the local administrator account that you will use to connect to the VM inside of Azure. Veeam utilizes port 6180 to connect out to Azure so you’ll need to make sure that port on the firewall is opened or specify a different port.

Veeam: Azure Proxy Server Local Account

Note: You CANNOT use ‘Administrator’ – If you do the Azure Proxy deployment will fail – “The remote server returned an error: (400) Bad Request. Also, within the Azure Activity log you will be able to see the failure message during the Write Virtualmachines task with the message – “The Admin Username specified is not allowed.”

Veeam: Bad Username Error

Azure Admin Username specified is not valid

Next choose your deployment model- Recommended is the Azure Resource Manager as the Classic model is being deprecated and should no longer be used!

Veeam: Azure Proxy Server Deployment Method

Previously we added our Azure Subscription details. Here is where we begin to leverage those credentials. Pick the corresponding Subscription as well as your appropriate Azure data center region.

Veeam: Azure Subscription

Next choose the size of the VM. In my testing I’ve been fine using a Basic_A2 and have not experienced any problems. However, if necessary you can select a larger sized VM. Also choose the storage account in which you would like to have the hard disks for this VM stored.

Veeam: Azure Proxy Server Size and Storage Account

The Resource Group selection step allows you to specify either an existing Resource Group or to create a new one. By default the Create a new resource group radio button is selected. In the new resource group, Veeam automatically creates the necessary network security group, public IP address as well as the network interface. You can however alter the public DNS name.

Veeam: Azure Proxy Server Deployment Select Resource Group

The last step in this process is to specify the virtual network and choose Next, Finish. Here you will see the Infrastructure Item Saving status window. If you accidentally close this window, navigate to the History and choose System Jobs.

Veeam: Azure Proxy Server Deployment Status

Within, you can view the Activity Log. Filter by Last Hour to see all operations that have taken place. Once the view refreshes you will see several operations taking place as the VM within Azure completes.

Azure: Activity Log


Azure: Operation Activity Log

Once the Deployment of the Azure Proxy Server completes, click close.

Veeam: Azure Proxy Server Deployment Complete!

Within Azure we now have our completely deployed and Stopped (Deallocated) Veeam Azure Proxy Server.

Azure: Stopped (Deallocated) Proxy Server

Within the Veeam UI you’ll now notice a new type of Proxy Server with the list of proxy’s – Azure

Veeam: Proxy Server Type = Azure

If you plan on restoring to Microsoft Azure you should definitely consider the Veeam Azure Proxy Server as must to deploy. It will save you time and bandwidth on the restoration process.

2 thoughts on “Veeam Direct Restore to Microsoft Azure: How to Deploy the Azure Proxy Server?

  • August 9, 2017 at 4:56 am


    I found this page from a google search as I was getting “The remote server returned an error: (400) Bad Request” error using the Add Azure Proxy wizard in Veeam 9.5u2.

    I had not used ‘administrator’ for the local admin account, but your post was helpful in finding the error in the Azure Activity Log so I thought I would share. The error Summary was pretty useless, but the JSON output showed the exact error…

    “details”:[{“code”:”VMSizeDoesntSupportPremiumStorage”,”message”:”Storage account type ‘Premium_LRS’ is not supported for VM size Basic_A2.”}]}}”

    Because I was deploying the most basic VM configuration (as recommended by Veeam) but had chose a premium storage account, these settings were not compatible. I created a new storage account of type ‘standard’ and used this for the proxy VM.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: