Release notes for Microsoft Azure Backup Server

This article provides the known issues and workarounds for Microsoft Azure Backup Server (MABS) V3.

Backup and recovery fails for clustered workloads

Description: Backup/restore fails for clustered data sources such as Hyper-V cluster or SQL cluster (SQL Always On) or Exchange in database availability group (DAG) after upgrading MABS V2 to MABS V3.

Work around: To prevent this, open SQL Server Management Studio (SSMS)) and run the following SQL script on the DPM DB:

    IF EXISTS (SELECT * FROM dbo.sysobjects
        WHERE id = OBJECT_ID(N'[dbo].[tbl_PRM_DatasourceLastActiveServerMap]')
        AND OBJECTPROPERTY(id, N'IsUserTable') = 1)
        DROP TABLE [dbo].[tbl_PRM_DatasourceLastActiveServerMap]
        GO

        CREATE TABLE [dbo].[tbl_PRM_DatasourceLastActiveServerMap] (
            [DatasourceId]          [GUID]          NOT NULL,
            [ActiveNode]            [nvarchar](256) NULL,
            [IsGCed]                [bit]           NOT NULL
            ) ON [PRIMARY]
        GO

        ALTER TABLE [dbo].[tbl_PRM_DatasourceLastActiveServerMap] ADD
    CONSTRAINT [pk__tbl_PRM_DatasourceLastActiveServerMap__DatasourceId] PRIMARY KEY NONCLUSTERED
        (
            [DatasourceId]
        )  ON [PRIMARY],

    CONSTRAINT [DF_tbl_PRM_DatasourceLastActiveServerMap_IsGCed] DEFAULT
        (
            0
        ) FOR [IsGCed]
    GO

Upgrade to MABS V3 fails in Russian locale

Description: Upgrade from MABS V2 to MABS V3 in Russian locale fails with an error code 4387.

Work around: Do the following steps to upgrade to MABS V3 using Russian install package:

  1. Backup your SQL database and uninstall MABS V2 (choose to retain the protected data during uninstall).
  2. Upgrade to SQL 2017 (Enterprise) and uninstall reporting as part of upgrade.
  3. Install SQL Server Reporting Services (SSRS).
  4. Install SQL Server Management Studio (SSMS).
  5. Configure Reporting using the parameters as documented in SSRS configuration with SQL 2017.
  6. Install MABS V3.
  7. Restore SQL using SSMS and run DPM-Sync tool as described here.
  8. Update the ‘DataBaseVersion’ property in dbo.tbl_DLS_GlobalSetting table using the following command:
        UPDATE dbo.tbl_DLS_GlobalSetting
        set PropertyValue = '13.0.415.0'
        where PropertyName = 'DatabaseVersion'
  1. Start MSDPM service.

Next steps

What's New in MABS V3