1. Introduction

This guide explains how to set up Backup Gateway on Microsoft Azure to store backups in the Azure cloud.

Typically, you will only need to create a VM with Acronis Software-Defined Infrastructure on Azure, specifying the required details like VM user name and password, credentials for a partner account in Acronis Backup Cloud, and such.

Once the virtual machine is running, you should be able to store backups in the Azure cloud, without having to log in to Acronis Software-Defined Infrastructure.

1.1. Important Requirements and Restrictions

  1. When working with public clouds, Backup Gateway uses the local storage (inside the VM) as the staging area as well as to keep service information. It means that the data to be uploaded to the cloud is first stored locally and only then sent to the destination. Because of this, you must make sure that the local storage is redundant and permanent. Using temporary disks may result in data loss.

  2. You must update Acronis Backup Agents to version 12.0.4492 (Windows/Mac) or 12.0.4470 (Linux). Otherwise agents’ attempts to place backups in the new storage backend will result in “Backup failed” errors.

  3. Choose a correct disk template to ensure desired backup performance (see example in the next paragraph). Make sure to plan ahead, because disk template cannot be changed. In such a case, you will need to add a new disk with the correct template to the VM, add the new disk to the storage cluster, release the old disk from the storage cluster, and delete it from the VM.

    Performance and size of a local VM disk depends on its template. For example, a STANDARD_DS1 virtual machine has the dedicated bandwidth of 32 MB/s for premium storage disk traffic. In turn, a P10 premium storage disk can provide the bandwidth of 100 MB/s. If a P10 premium storage disk is attached to a STANDARD_DS1 virtual machine, its performance will be capped at 32 MB/s instead of the maximum 100 MB/s it can provide. For more details on premium storage, see Azure documentation.