Merge pull request #310714 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-21 12:00 UTC

Author: learn-build-service-prod[bot]

articles/backup/backup-azure-microsoft-azure-backup.md

@@ -2,7 +2,7 @@
 title: Use Azure Backup Server to back up workloads
 description: In this article, learn how to prepare your environment to protect and back up workloads using Microsoft Azure Backup Server (MABS).
 ms.topic: how-to
-ms.date: 07/15/2025
+ms.date: 01/21/2026
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -64,15 +64,15 @@ You can deduplicate the DPM storage using Windows Server Deduplication. Learn mo
 > [!NOTE]
 > 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 system
+> * A computer running as a domain controller.
+> * A computer that has the Application Server role installed.
+> * A computer that's a System Center Operations Manager management server.
+> * A computer that has running Exchange Server.
+> * A computer that's a node of a system.
 >
 > 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*.
+Always join Azure Backup Server to a domain. Moving an existing Azure Backup Server machine to a new domain after deployment isn't supported.
 
 Whether you send backup data to Azure, or keep it locally, Azure Backup Server must be registered with a Recovery Services vault.
 
@@ -87,68 +87,58 @@ The storage replication option allows you to choose between geo-redundant storag
 
 To edit the storage replication setting:
 
-1. From the **Recovery Services vaults** pane, select the new vault. Under the **Settings** section, select  **Properties**.
-2. In **Properties**, under **Backup Configuration**, select **Update**.
+1. On the **Recovery Services vaults** pane, select the new vault. 
+1. On the **Recovery Services vaults** you selected, go to **Settings** > **Properties**.
+1. On the **Properties** pane, under **Backup Configuration**, select **Update**.
 
-3. Select the storage replication type, and select **Save**.
+   :::image type="content" source="./media/backup-create-rs-vault/recovery-services-vault-backup-configuration.png" alt-text="Screenshot that shows the selection of the storage replication type for the new Recovery Services vault." lightbox="./media/backup-create-rs-vault/recovery-services-vault-backup-configuration.png":::
 
-     ![Set the storage configuration for new vault](./media/backup-create-rs-vault/recovery-services-vault-backup-configuration.png)
+1. On the **Backup Configuration** pane, select the storage replication type, and then select **Apply**.
 
 ## Software package
 
-### Downloading the software package
+### Download the MABS software package
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-2. 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**.
+2. On the search box, type **Recovery**, and then select **Recovery Services vaults** from the search results.
 
-   * 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.
+   :::image type="content" source="./media/backup-azure-microsoft-azure-backup/open-recovery-services-vault.png" alt-text="Screenshot that shows how to open the Recovery Services vaults pane in the Azure portal.":::
 
-     ![Create Recovery Services vault step 1](./media/backup-azure-microsoft-azure-backup/open-recovery-services-vault.png)
+1. On the **Recovery Services vaults** pane, select the new vault you created.
 
-     The list of Recovery Services vaults appears.
-   * From the list of Recovery Services vaults, select a vault.
+1. On the vault dashboard, under **Getting Started**, select **Backup**.
 
-     The selected vault dashboard opens.
+   :::image type="content" source="./media/backup-azure-microsoft-azure-backup/vault-dashboard.png" alt-text="Screenshot that shows the dashboard of the selected Recovery Services vault." lightbox="./media/backup-azure-microsoft-azure-backup/vault-dashboard.png":::
 
-     ![Vault dashboard](./media/backup-azure-microsoft-azure-backup/vault-dashboard.png)
-3. The **Settings** pane opens up by default. If it's closed, select **Settings** to open the settings pane.
+1. On the **Backup** pane, from the **Where is your workload running** menu, select **On-premises**.
 
-    ![Settings pane](./media/backup-azure-microsoft-azure-backup/vault-setting.png)
-4. Select **Backup** to open the Getting Started wizard.
+    :::image type="content" source="./media/backup-azure-microsoft-azure-backup/backup-goals-azure-backup-server.png" alt-text="Screenshot that shows the selection of workloads to protect using Azure Backup Server.":::
 
-    ![Backup getting started](./media/backup-azure-microsoft-azure-backup/getting-started-backup.png)
+    From the **What do you want to back up?** drop-down menu, select the workloads you want to protect using Azure Backup Server.
 
-    In the **Getting Started with backup** pane that opens, **Backup Goals** will be auto-selected.
-
-    ![Backup-goals-default-opened](./media/backup-azure-microsoft-azure-backup/getting-started.png)
-
-5. In the **Backup Goal** pane, from the **Where is your workload running** menu, select **On-premises**.
-
-    ![on-premises and workloads as goals](./media/backup-azure-microsoft-azure-backup/backup-goals-azure-backup-server.png)
-
-    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.
+1. To back up workloads to Azure, select **Prepare Infrastructure** option.
 
    > [!NOTE]
    > 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](./backup-windows-with-mars-agent.md). 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.
    >
    >
 
-    ![Getting Started wizard change](./media/backup-azure-microsoft-azure-backup/getting-started-prep-infra.png)
+   :::image type="content" source="./media/backup-azure-microsoft-azure-backup/select-prepare-infrastructure.png" alt-text="Screenshot that shows the Prepare infrastructure option selected in the Backup Goals pane.":::
+
+1. On the **Prepare infrastructure** pane, for **Install MicrosoftAzure Backup Server** and **Download vault credentials**, select the **Download** links.
 
-6. 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.
+   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.
 
-    ![Prepare infrastructure for Azure Backup Server](./media/backup-azure-microsoft-azure-backup/azure-backup-server-prep-infra.png)
+   :::image type="content" source="./media/backup-azure-microsoft-azure-backup/azure-backup-server-prep-infra.png" alt-text="Screenshot that shows the Prepare infrastructure pane with download links for Microsoft Azure Backup Server and vault credentials.":::
 
-7. 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.
+1. On the **Microsoft Azure Backup Server download** page, select **Download**.
+1. On the MABS version selection window, select all the files and then select **Download**. Download all the files coming in from the Microsoft Azure Backup Server download page, and place all the files in the same folder.
 
-    ![Download center 1](./media/backup-azure-microsoft-azure-backup/downloadcenter.png)
+   :::image type="content" source="./media/backup-azure-microsoft-azure-backup/downloadcenter.png" alt-text="Screenshot that shows the Download Center with Microsoft Azure Backup Server files.":::
 
-    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.
+    Since the download size of all the files together is > 3 GB, on a 10-Mbps download link it might take up to 60 minutes for the download to complete.
 
-### Extracting the software package
+### Extract the MABS 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.
 
@@ -157,11 +147,11 @@ After you've downloaded all the files, select **MicrosoftAzureBackupInstaller.ex
 >
 >
 
-![Setup extracting files for install](./media/backup-azure-microsoft-azure-backup/extract/03.png)
+:::image type="content" source="./media/backup-azure-microsoft-azure-backup/extract/03.png" alt-text="Screenshot that shows the setup files extraction wizard for install.":::
 
-Once the extraction process completes, check the box to launch the freshly extracted *setup.exe* to begin installing Microsoft Azure Backup Server and select the **Finish** button.
+After the extraction process completes, 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
+### Install the software package
 
 1. Select **Microsoft Azure Backup Server** to launch the setup wizard.
 
@@ -270,7 +260,7 @@ The following sections describe how to update protection agents for client compu
 
 ## 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.
+Here are the steps if you need to move MABS to a new server, while retaining the storage. This can be done only if the data is on Modern Backup Storage.
 
   > [!IMPORTANT]
   >
@@ -286,7 +276,7 @@ Here are the steps if you need to move MABS to a new server, while retaining the
 7. Restore the DPMDB taken in step 1.
 8. Attach the storage from the original backup server to the new server.
 9. From SQL, restore the DPMDB.
-10. Run CMD (as an administrator) on the new server. Go to the Microsoft Azure Backup install location and bin folder.
+10. Run CMD (as an administrator) on the new server. Go to the Microsoft Azure Backup installed location and bin folder.
 
     Path example:
     `C:\windows\system32>cd "c:\Program Files\Microsoft Azure Backup\DPM\DPM\bin\"`
@@ -357,7 +347,7 @@ Use the following procedures to upgrade MABS.
 
 > [!NOTE]
 >
-> MABS V3 isn't a prerequisite for installing MABS V4. However, you can upgrade to MABS V4 only from MABS V3 (RTM, Update Rollup 1 and Update Rollup 2).
+> MABS V3 isn't a prerequisite for installing MABS V4. However, you can upgrade to MABS V4 only from MABS V3 (RTM, Update Rollup 1, Update Rollup 2).
 
 Use the following steps to upgrade MABS:
 
@@ -387,9 +377,9 @@ The example below increases the limit to 12 jobs.
 
   "6e7c76f4-a832-4418-a772-8e58fd7466cb"=dword:0000000C
 
-## Troubleshooting
+## Troubleshoot MABS installation issues
 
-If Microsoft Azure Backup server fails with errors during the setup phase (or backup or restore), refer to this [error codes document](https://support.microsoft.com/kb/3041338)  for more information.
+If Microsoft Azure Backup server fails with errors during the setup, backup, or restore phase, see this [error codes document](https://support.microsoft.com/kb/3041338)  for more information.
 
 You can also refer to [Azure Backup related FAQs](backup-azure-backup-faq.yml).
 

articles/backup/media/backup-azure-microsoft-azure-backup/azure-backup-server-prep-infra.png

@@ -26,8 +26,8 @@ This article summarizes the scenarios supported and limitations present when you
 | ------- | -------- | -------- |
 | **Topology** | SAP ASE Database running in Azure Linux VMs only. | Windows |
 | **Regions**                   | **Americas** – Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US, Canada Central, Canada East, Brazil South <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India, China East, China East 2, China East 3, China North, China North 2, China North 3 <br> **Europe** – West Europe, North Europe, France Central, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North, Norway East, Norway West, Sweden Central, Sweden South <br> **Africa / ME** - South Africa North, South Africa West, UAE North, UAE Central  <BR>  **Azure Government regions** | France South, Germany Central, Germany Northeast, US Gov IOWA |
-| **OS versions** | SLES 12 with SP0, SP1, SP2, SP3, SP4, and SP5; SLES 15 with SP0, SP1, SP2, SP3, SP4, and SP5, 15.6 <br><br> RHEL 7.1, 7.2, 7.3, 7.4, 7.6, 7.7, 7.9, 8.1, 8.2, 8.3, 8.4,8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 9.2 |  |
-| **ASE versions** | SAP Adaptive Server Enterprise 16.0 SP02, SP03, SP04 |  |
+| **OS versions** | SLES 12 with SP0, SP1, SP2, SP3, SP4, and SP5; SLES 15 with SP0, SP1, SP2, SP3, SP4, and SP5, 15.6, 15.7 <br><br> RHEL 8.1, 8.2, 8.3, 8.4,8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 9.2, 9.4, 9.6 |  |
+| **ASE versions** | SAP Adaptive Server Enterprise 16.0 SP02, SP03, SP04, ASE version 16.1 |  |
 | **ASE Instances** | A single SAP ASE instance on a single Azure Virtual Machine (VM). <br><br> Multi SID on single VM. | HA on single VM isn't currently supported. |
 | **Backup types** | Full, Differential, and Log backups. | Incremental, archival support is currently not available. |
 | **Restore types** | ALR-Alternate Location Restore, OLR-Original Location Restore (In-Place), Restore as Files.  |  |
@@ -40,6 +40,7 @@ This article summarizes the scenarios supported and limitations present when you
 | **Security Capabilities** | Immutability, Soft Delete, MUA, Private Endpoint, and Encryption at rest are supported. | |
 
 >[!NOTE]
+>- Note that the Linux OS versions being used should not be in a "deprecated", "limited extended support" or "End-of-life" stages by their respective vendors. Any versions entering the mentioned stages by their vendors will also subsequently get "out of support" from Azure Backup.
 >- Azure Backup doesn’t automatically adjust for daylight saving time changes when backing up an SAP ASE (Sybase) database running in an Azure VM. We recommend you to modify the policy manually as needed.
 >- You can now monitor the backup and restore jobs (to the same machine) triggered from ASE native clients (SAP ASE Studio/Cockpit/DBA Cockpit) in the Azure portal.
 

articles/backup/media/backup-azure-microsoft-azure-backup/backup-goals-azure-backup-server.png

@@ -21,7 +21,7 @@ You can use Azure Backup to back up SQL Server databases in Azure VMs hosted on
 **Supported deployments** | SQL Marketplace Azure VMs and non-Marketplace (SQL Server manually installed) VMs are supported.
 **Supported regions** | Azure Backup for SQL Server databases is available in all regions, except France South (FRS).
 **Supported operating systems** | Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 (all versions), Windows Server 2008 R2 SP1 <br/><br/> Additional configuration is required for Windows Server 2008 and 2008 R2. Learn how to [set VM permission](backup-azure-sql-database.md#set-vm-permissions). <br><br> Linux isn't currently supported. 
-**Supported SQL Server versions** | SQL Server 2022 Express, SQL Server 2022, SQL Server 2019, SQL Server 2017 as detailed on the [Search product lifecycle page](/lifecycle/products/sql-server-2017), SQL Server 2016 and SPs as detailed on the [Search product lifecycle page](https://support.microsoft.com/lifecycle/search?alpha=SQL%20server%202016%20service%20pack), SQL Server 2014, SQL Server 2012. <br/><br/> Enterprise, Standard, Web, Developer, Express.<br><br>Express Local DB versions aren't supported.
+**Supported SQL Server versions** | SQL Server 2022 Express, SQL Server 2022, SQL Server 2019, SQL Server 2017 as detailed on the [Search product lifecycle page](/lifecycle/products/sql-server-2017), SQL Server 2016 and SPs as detailed on the [Search product lifecycle page](https://support.microsoft.com/lifecycle/search?alpha=SQL%20server%202016%20service%20pack), SQL Server 2014, SQL Server 2012. <br/><br/> Enterprise, Standard, Web, Developer, Express.<br><br>Express Local DB versions aren't supported.<br><br>Limited support is available for SQL Server versions that are currently in "End of life", "Extended Security Updates" or any other limited support phases.
 **Supported .NET versions** | .NET Framework 4.6.2 or later installed on the VM
 **Supported deployments** | SQL Marketplace Azure VMs and non-Marketplace (SQL Server that is manually installed) VMs are supported. Support for standalone instances is always on [availability groups](backup-sql-server-on-availability-groups.md). <br><br>  Note that the SQL databases that are part of a AlwaysOn AG and are synced from SQL Managed Instance aren't supported.
 **Cross Region Restore** | Supported for databases protected as a standalone instance and/or as part of a SQL availability group . [Learn more](restore-sql-database-azure-vm.md#cross-region-restore).