Install and upgrade Azure Backup Server
Applies To: MABS v3. (MABS v2 is no longer supported. If you're using a version earlier than MABS v3, please upgrade to the latest version.)
This article explains how to prepare your environment to back up workloads using Microsoft Azure Backup Server (MABS). With Azure Backup Server, you can protect application workloads such as Hyper-V VMs, Microsoft SQL Server, SharePoint Server, Microsoft Exchange, and Windows clients from a single console.
Azure Backup Server can now protect VMware VMs and provides improved security capabilities. Install the product as explained in the sections below and the latest Azure Backup Agent. To learn more about backing up VMware servers with Azure Backup Server, see the article, Use Azure Backup Server to back up a VMware server. To learn about security capabilities, refer to Azure Backup security features documentation.
MABS deployed in an Azure VM can back up VMs in Azure but they should be in same domain to enable backup operation. The process to back an Azure VM remains same as backing up VMs on premises, however deploying MABS in Azure has some limitations. For more information on limitation, see DPM as an Azure virtual machine.
Azure has two deployment models for creating and working with resources: Resource Manager and classic. This article provides the information and procedures for restoring VMs deployed using the Resource Manager model.
Azure Backup Server inherits much of the workload backup functionality from Data Protection Manager (DPM). This article links to DPM documentation to explain some of the shared functionality. Though Azure Backup Server shares much of the same functionality as DPM, Azure Backup Server doesn't back up to tape, nor does it integrate with System Center.
Choose an installation platform
The first step towards getting the Azure Backup Server up and running is to set up a Windows Server. Your server can be in Azure or on-premises.
- To protect on-premises workloads, the MABS server must be located on-premises, and connected to a domain.
- To protect workloads running on Azure VMs, the MABS server must be located in Azure, running as an Azure VM, and connected to a domain.
Using a server in Azure
When choosing a server for running Azure Backup Server, it's recommended you start with a gallery image of Windows Server 2016 Datacenter or Windows Server 2019 Datacenter. The article, Create your first Windows virtual machine in the Azure portal, provides a tutorial for getting started with the recommended virtual machine in Azure, even if you've never used Azure before. The recommended minimum requirements for the server virtual machine (VM) should be: Standard_A4_v2 with four cores and 8-GB RAM.
Protecting workloads with Azure Backup Server has many nuances. The protection matrix for MABS helps explain these nuances. Before deploying the machine, read this article completely.
Using an on-premises server
If you don't want to run the base server in Azure, you can run the server on a Hyper-V VM, a VMware VM, or a physical host. The recommended minimum requirements for the server hardware are two cores and 8-GB RAM. The supported operating systems are listed in the following table:
|Windows Server 2019||64 bit||Standard, Datacenter, Essentials|
|Windows Server 2016 and latest SPs||64 bit||Standard, Datacenter, Essentials|
You can deduplicate the DPM storage using Windows Server Deduplication. Learn more about how DPM and deduplication work together when deployed in Hyper-V VMs.
Azure Backup Server is designed to run on a dedicated, single-purpose server. You can't install Azure Backup Server on:
- A computer running as a domain controller
- A computer on which the Application Server role is installed
- A computer that's a System Center Operations Manager management server
- A computer on which Exchange Server is running
- A computer that's a node of a cluster
Installing Azure Backup Server isn't supported on Windows Server Core or Microsoft Hyper-V Server.
Always join Azure Backup Server to a domain. Moving an existing Azure Backup Server machine to a new domain after deployment is not supported.
Whether you send backup data to Azure, or keep it locally, Azure Backup Server must be registered with a Recovery Services vault.
If you encounter difficulties to register to a vault or other errors, ensure that you've the MARS agent version 2.0.9249.0 or above installed. If not, we recommend you to install the latest version from here.
Create a Recovery Services vault
A Recovery Services vault is a management entity that stores recovery points that are created over time, and it provides an interface to perform backup-related operations. These operations include taking on-demand backups, performing restores, and creating backup policies.
To create a Recovery Services vault:
Sign in to the Azure portal.
Search for Backup center, and then go to the Backup center dashboard.
On the Overview pane, select Vault.
Select Recovery Services vault > Continue.
On the Recovery Services vault pane, enter the following values:
Subscription: Select the subscription to use. If you're a member of only one subscription, you'll see that name. If you're not sure which subscription to use, use the default subscription. There are multiple choices only if your work or school account is associated with more than one Azure subscription.
Resource group: Use an existing resource group or create a new one. To view a list of available resource groups in your subscription, select Use existing, and then select a resource in the dropdown list. To create a new resource group, select Create new, and then enter the name. For more information about resource groups, see Azure Resource Manager overview.
Vault name: Enter a friendly name to identify the vault. The name must be unique to the Azure subscription. Specify a name that has at least 2 but not more than 50 characters. The name must start with a letter and consist only of letters, numbers, and hyphens.
Region: Select the geographic region for the vault. For you to create a vault to help protect any data source, the vault must be in the same region as the data source.
If you're not sure of the location of your data source, close the window. Go to the list of your resources in the portal. If you have data sources in multiple regions, create a Recovery Services vault for each region. Create the vault in the first location before you create a vault in another location. There's no need to specify storage accounts to store the backup data. The Recovery Services vault and Azure Backup handle that automatically.
After you provide the values, select Review + create.
When you're ready to finish creating the Recovery Services vault, select Create.
It can take a while to create the Recovery Services vault. Monitor the status notifications in the Notifications area at the upper right. After your vault is created, it's visible in the list of Recovery Services vaults. If your vault isn't displayed, select Refresh.
Set storage replication
The storage replication option allows you to choose between geo-redundant storage and locally redundant storage. By default, Recovery Services vaults use geo-redundant storage. If this vault is your primary vault, leave the storage option set to geo-redundant storage. Choose locally redundant storage if you want a cheaper option that isn't quite as durable. Read more about geo-redundant, locally redundant, and zone-redundant storage options in the Azure Storage replication overview.
To edit the storage replication setting:
From the Recovery Services vaults pane, select the new vault. Under the Settings section, select Properties.
In Properties, under Backup Configuration, select Update.
Select the storage replication type, and select Save.
Downloading the software package
Sign in to the Azure portal.
If you already have a Recovery Services vault open, continue to step 3. If you don't have a Recovery Services vault open, but are in the Azure portal, on the main menu, select Browse.
In the list of resources, type Recovery Services.
As you begin typing, the list will filter based on your input. When you see Recovery Services vaults, select it.
The list of Recovery Services vaults appears.
From the list of Recovery Services vaults, select a vault.
The selected vault dashboard opens.
The Settings pane opens up by default. If it's closed, select Settings to open the settings pane.
Select Backup to open the Getting Started wizard.
In the Getting Started with backup pane that opens, Backup Goals will be auto-selected.
In the Backup Goal pane, from the Where is your workload running menu, select On-premises.
From the What do you want to back up? drop-down menu, select the workloads you want to protect using Azure Backup Server, and then select OK.
The Getting Started with backup wizard switches the Prepare infrastructure option to back up workloads to Azure.
If you only want to back up files and folders, we recommend using the Azure Backup agent and following the guidance in the article, First look: back up files and folders. If you're going to protect more than files and folders, or you're planning to expand the protection needs in the future, select those workloads.
In the Prepare infrastructure pane that opens, select the Download links for Install Azure Backup Server and Download vault credentials. You use the vault credentials during registration of Azure Backup Server to the Recovery Services vault. The links take you to the Download Center where the software package can be downloaded.
Select all the files and select Next. Download all the files coming in from the Microsoft Azure Backup download page, and place all the files in the same folder.
Since the download size of all the files together is > 3 GB, on a 10-Mbps download link it may take up to 60 minutes for the download to complete.
Extracting the software package
After you've downloaded all the files, select MicrosoftAzureBackupInstaller.exe. This will start the Microsoft Azure Backup Setup Wizard to extract the setup files to a location specified by you. Continue through the wizard and select the Extract button to begin the extraction process.
At least 4 GB of free space is required to extract the setup files.
Once the extraction process complete, check the box to launch the freshly extracted setup.exe to begin installing Microsoft Azure Backup Server and select the Finish button.
Installing the software package
Select Microsoft Azure Backup to launch the setup wizard.
On the Welcome screen, select the Next button. This takes you to the Prerequisite Checks section. On this screen, select Check to determine if the hardware and software prerequisites for Azure Backup Server have been met. If all prerequisites are met successfully, you'll see a message indicating that the machine meets the requirements. Select the Next button.
The Azure Backup Server installation package comes bundled with the appropriate SQL Server binaries needed. When starting a new Azure Backup Server installation, pick the option Install new Instance of SQL Server with this Setup and select the Check and Install button. Once the prerequisites are successfully installed, select Next.
If you wish to use your own SQL server, the supported SQL Server versions are SQL Server 2014 SP1 or higher, 2016 and 2017. All SQL Server versions should be Standard or Enterprise 64-bit. Azure Backup Server won't work with a remote SQL Server instance. The instance being used by Azure Backup Server needs to be local. If you're using an existing SQL server for MABS, the MABS setup only supports the use of named instances of SQL server.
If a failure occurs with a recommendation to restart the machine, do so and select Check Again. If there are any SQL configuration issues, reconfigure SQL according to the SQL guidelines and retry to install/upgrade MABS using the existing instance of SQL.
When you use your own instance of SQL, make sure you add builtin\Administrators to sysadmin role to master DB.
SSRS Configuration with SQL 2017
When you're using your own instance of SQL 2017, you need to manually configure SSRS. After SSRS configuration, ensure that IsInitialized property of SSRS is set to True. When this is set to True, MABS assumes that SSRS is already configured and will skip the SSRS configuration.
Use the following values for SSRS configuration:
- Service Account: ‘Use built-in account’ should be Network Service
- Web Service URL: ‘Virtual Directory’ should be ReportServer_<SQLInstanceName>
- Database: DatabaseName should be ReportServer$<SQLInstanceName>
- Web Portal URL: ‘Virtual Directory’ should be Reports_<SQLInstanceName>
Learn more about SSRS configuration.
Licensing for SQL Server used as the database for MABS is governed by Microsoft Online Services Terms (OST). According to OST, SQL Server bundled with MABS can be used only as the database for MABS.
Provide a location for the installation of Microsoft Azure Backup server files and select Next.
The scratch location is a requirement for back up to Azure. Ensure the scratch location is at least 5% of the data planned to be backed up to the cloud. For disk protection, separate disks need to be configured once the installation completes. For more information about storage pools, see Prepare data storage.
Capacity requirements for disk storage depend primarily on the size of the protected data, the daily recovery point size, expected volume data growth rate, and retention range objectives. We recommend you make the disk storage twice size of the protected data. This assumes a daily recovery point size that's 10% of the protected data size and a 10 days retention range. To get a good estimate of size, review the DPM Capacity Planner.
Provide a strong password for restricted local user accounts and select Next.
Select whether you want to use Microsoft Update to check for updates and select Next.
We recommend having Windows Update redirect to Microsoft Update, which offers security and important updates for Windows and other products like Microsoft Azure Backup Server.
Review the Summary of Settings and select Install.
The installation happens in phases. In the first phase, the Microsoft Azure Recovery Services Agent is installed on the server. The wizard also checks for Internet connectivity. If Internet connectivity is available, you can continue with the installation. If not, you need to provide proxy details to connect to the Internet.
If you run into errors in vault registration, ensure that you're using the latest version of the MARS agent, instead of the version packaged with MABS server. You can download the latest version from here and replace the MARSAgentInstaller.exe file in System Center Microsoft Azure Backup Server v3\MARSAgent folder before installation and registration on new servers.
The next step is to configure the Microsoft Azure Recovery Services Agent. As a part of the configuration, you'll have to provide your vault credentials to register the machine to the Recovery Services vault. You'll also provide a passphrase to encrypt/decrypt the data sent between Azure and your premises. You can automatically generate a passphrase or provide your own minimum 16-character passphrase. Continue with the wizard until the agent has been configured.
Once registration of the Microsoft Azure Backup server successfully completes, the overall setup wizard proceeds to the installation and configuration of SQL Server and the Azure Backup Server components. Once the SQL Server component installation completes, the Azure Backup Server components are installed.
When the installation step has completed, the product's desktop icons will have been created as well. Double-click the icon to launch the product.
Add backup storage
The first backup copy is kept on storage attached to the Azure Backup Server machine. For more information about adding disks, see Configure storage pools and disk storage.
You need to add backup storage even if you plan to send data to Azure. In the current architecture of Azure Backup Server, the Azure Backup vault holds the second copy of the data while the local storage holds the first (and mandatory) backup copy.
Install and update the Data Protection Manager protection agent
MABS uses the System Center Data Protection Manager protection agent. Here are the steps to install the Protection Agent on your Protection Servers.
The following sections describe how to update protection agents for client computers.
In the Backup Server Administrator Console, select Management > Agents.
In the display pane, select the client computers for which you want to update the protection agent.
The Agent Updates column indicates when a protection agent update is available for each protected computer. In the Actions pane, the Update action is available only when a protected computer is selected and updates are available.
To install updated protection agents on the selected computers, in the Actions pane, select Update.
For a client computer that isn't connected to the network, until the computer is connected to the network, the Agent Status column shows a status of Update Pending.
After a client computer is connected to the network, the Agent Updates column for the client computer shows a status of Updating.
Move MABS to a new server
Here are the steps if you need to move MABS to a new server, while retaining the storage. This can be done only if all the data is on Modern Backup Storage.
- The new server name must have the same name as the original Azure Backup Server instance. You can't change the name of the new Azure Backup Server instance if you want to use the previous storage pool and MABS Database (DPMDB) to retain recovery points.
- You must have a backup of the MABS Database (DPMDB). You'll need it to restore the database.
In the display pane, select the client computers for which you want to update the protection agent.
Shut down the original Azure Backup server or take it offline.
Reset the machine account in Active Directory.
Install Server 2016 on a new machine and give it the same machine name as the original Azure Backup server.
Join the domain.
Install Azure Backup Server V3 or later (move MABS Storage pool disks from old server and import).
Restore the DPMDB taken in step 1.
Attach the storage from the original backup server to the new server.
From SQL, restore the DPMDB.
Run CMD (as an administrator) on the new server. Go to the Microsoft Azure Backup install location and bin folder.
C:\windows\system32>cd "c:\Program Files\Microsoft Azure Backup\DPM\DPM\bin\"
To connect to Azure Backup, run
If you've added new disks to the DPM Storage pool instead of moving the old ones, then run
Azure Backup Server requires connectivity to the Azure Backup service for the product to work successfully. To validate whether the machine has the connectivity to Azure, use the
Get-DPMCloudConnection cmdlet in the Azure Backup Server PowerShell console. If the output of the cmdlet is TRUE, then connectivity exists, otherwise there's no connectivity.
At the same time, the Azure subscription needs to be in a healthy state. To find out the state of your subscription and to manage it, sign in to the subscription portal.
Once you know the state of the Azure connectivity and of the Azure subscription, you can use the table below to find out the impact on the backup/restore functionality offered.
|Connectivity State||Azure Subscription||Back up to Azure||Back up to disk||Restore from Azure||Restore from disk|
|Connected||Deprovisioned||Stopped||Stopped||Stopped and Azure recovery points deleted||Stopped|
|Lost connectivity > 15 days||Active||Stopped||Stopped||Allowed||Allowed|
|Lost connectivity > 15 days||Expired||Stopped||Stopped||Allowed||Allowed|
|Lost connectivity > 15 days||Deprovisioned||Stopped||Stopped||Stopped and Azure recovery points deleted||Stopped|
Recovering from loss of connectivity
If your machine has limited internet access, ensure that firewall settings on the machine or proxy allow the following URLs and IP addresses:
- IP addresses
If you're using ExpressRoute Microsoft peering, select the following services/regions:
- Azure Active Directory (12076:5060)
- Microsoft Azure Region (according to the location of your Recovery Services vault)
- Azure Storage (according to the location of your Recovery Services vault)
For more details, visit ExpressRoute routing requirements.
Once connectivity to Azure has been restored to the Azure Backup Server machine, the operations that can be performed are determined by the Azure subscription state. The table above has details about the operations allowed once the machine is "Connected".
Handling subscription states
It's possible to take an Azure subscription from an Expired or Deprovisioned state to the Active state. However, this has some implications on the product behavior when the state isn't Active:
- A Deprovisioned subscription loses functionality for the period that it's deprovisioned. On turning Active, the product functionality of backup/restore is revived. The backup data on the local disk also can be retrieved if it was kept with a sufficiently large retention period. However, the backup data in Azure is irretrievably lost once the subscription enters the Deprovisioned state.
- An Expired subscription only loses functionality for until it has been made Active again. Any backups scheduled for the period that the subscription was Expired won't run.
Use the following procedures to upgrade MABS.
Upgrade from MABS V2 to V3
MABS V2 isn't a prerequisite for installing MABS V3. However, you can upgrade to MABS V3 only from MABS V2.
Use the following steps to upgrade MABS:
To upgrade from MABS V2 to MABS V3, upgrade your OS to Windows Server 2016 or Windows Server 2019 if needed.
Upgrade your server. The steps are similar to installation. However, for SQL settings, you'll get an option to upgrade your SQL instance to SQL 2017, or to use your own instance of SQL server 2017.
Don't exit while your SQL instance is being upgraded. Exiting will uninstall the SQL reporting instance and so an attempt to re-upgrade MABS will fail.
As part of SQL 2017 upgrade, we backup the SQL encryption keys and uninstall the reporting services. After SQL server upgrade, reporting service(14.0.6827.4788) is installed & encryption keys are restored.
When configuring SQL 2017 manually, refer to SSRS configuration with SQL 2017 section under Install instructions.
Update the protection agents on the protected servers.
Backups should continue without the need to restart your production servers.
You can begin protecting your data now. If you're upgrading to Modern Backup Storage, while protecting, you can also choose the volumes you wish to store the backups in, and check for under provisioned space. Learn more.
If Microsoft Azure Backup server fails with errors during the setup phase (or backup or restore), refer to this error codes document for more information.
You can also refer to Azure Backup related FAQs.
You can get detailed information here about preparing your environment for DPM. It also contains information about supported configurations on which Azure Backup Server can be deployed and used. You can use a series of PowerShell cmdlets for performing various operations.
You can use these articles to gain a deeper understanding of workload protection using Microsoft Azure Backup server.
Submit and view feedback for