Update Rollup 1 for Microsoft Azure Backup Server V4

Introduction

This article describes the issues that are fixed in Update Rollup 1 for Microsoft Azure Backup Server V4 (MABS V4). This article also contains the installation instructions for this update.

Note: Existing Microsoft Azure Backup Server customers should upgrade to the latest agent (version 2.0.9249.0 or later). If the latest agent is not installed, online backups may fail, and no Microsoft Azure Backup Server operation will work. 

Note: Update Rollup 1 for MABS V4 is superseded by Update Rollup 1 Refresh for MABS V4 due to the following known issues:

Known issues:

1. Hyper-V scheduled backups take a long time to complete because each backup job triggers a consistency check.
   Error Message: The replica of Microsoft Hyper-V RCT on <Machine Name> is not consistent with the protected data source. DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. (ID 30135)

2. MABS console occasionally crashes when SMTP alerts or reports are configured.

Mitigation:

• If you have already installed UR1 for MABS V4, install UR1 Refresh for MABS V4 to resolve the issues listed above.

• If you have not installed UR1 for MABS V4, install UR1 Refresh for MABS V4 directly.

Reach out to Microsoft Support for queries or additional information. 

Issues that are fixed

This update fixes the following issues:

• Increase timeout of MABS Jobs and mount for online jobs to 30 days from 20 and 14 days respectively to enable backup of multi-TB data sources.

• Restore of VM live migrated from Host A to Host B and back to Host A fails with ID 958.

• Installing KB5021128 for SQL2016 or KB5021127 for SQL2017 prevents discovery of SQL databases for protection.

• Hyper-V item level recoveries fail with ID 958, internal error code 0x80990F4E if recovery point could not be mounted.

• Recovering file data from online recovery point to original location marks the replica as inconsistent.

• BMR backup creates additional snapshot on the protected server.

• Hyper-V backups does not remove avhdx files that are not required for backup.

• Tape Backup of VMware VM does not backup .vmdk disk.

• MABS occasionally crashes while enumerating volumes for protection.

• MABS storage pool volumes are occasionally marked as missing due to failed WMI queries.

• BMR backup sometimes fails with ID 104 - the process cannot access the file because it is being used by another process (0x80070020).

• Hyper-V VM recovery fails with ID 104 - unexpected error occurred while the job was running, unknown error (0x80041024).

• External DPM Server feature sometimes does not list all protected servers.

• Reports email subject and body is not localized.

• VMware VM restore fails with InvalidDeviceSpec error if networking configurations do not match for the source virtual distributed switches.

• Recovering a VMware VM which has a disk excluded recovers all disks.

• DPMSYNC command crashes after a server rebuild when VMware servers are protected.

• Hyper-V VM backup and restore fail with ID 60, the protection agent was in an unexpected state, internal error code (0x809909B0).

Note: A fresh installation of the Update Rollup agent could cause a restart of the protected server.

Other Improvements and Features

• MABS V4 UR1 also has additional new features introduced. For details on the new features, refer to the documentation here.

Known issues

No known issues.

How to obtain Update Rollup 1 for Microsoft Azure Backup Server V4

Update packages for Data Protection Manager are available from Microsoft Update or by manual download.

Installation instructions for Microsoft Azure Backup Server

To install this update for Microsoft Azure Backup Server, follow these steps:

1. Before you install this update, make a backup of the Microsoft Azure Backup Server database.

2. Install this rollup package on the server that's running Microsoft Azure Backup Server V4. To do this, run Microsoft Update on the server.

3. In the Data Protection Manager Administrator Console, update the protection agents. To do this, use one of the following methods.

Note: You need to restart protected servers to create or change protection groups.

Method 1: Update the protection agents from the Microsoft Azure Backup Server Administrator Console

1. Open the Microsoft Azure Backup Server Administrator Console.

2. Select the Management tab, and then select the Agents tab.

   1. In the Protected Computer list, select a computer, and then select Update on the Action pane.

3. Select Yes, and then select Update Agents.

Method 2: Update the protection agents on the protected servers

1. Obtain the updated protection agent package from the installation directory of the Microsoft Azure Backup Server at following path: Microsoft Azure Backup Server V4\DPM\DPM\agents\RA\14.0.42.0\amd64\1033\DPMAgentInstaller_KB5032421_AMD64.exe

2. Run the DPMAgentInstaller_KB5032421_AMD64.exe package on each protected server.

3. Open the Data Protection Manager Administrator Console on the System Center Data Protection Manager server 2022.

4. Select the Management tab, and then select the Agents tab. Select the protected server, refresh the information, and then verify that the agent version number is 14.0.42.0