Applies to: Microsoft Azure Backup Server V4 UR1 Refresh, Data Protection Manager 2022 UR2, Data Protection Manager 2025 RTM

Introduction

A VMware VM can enter power-off mode when a backup (Initial Replication (IR)/Delta Replication (DR)/ Consistency Check (CC)) running on DPM/MABS gets cancelled. This issue has been seen occurring on VMware ESXi 8.0 hosts.

Mitigation:

  • If you have already installed any of the following versions — MABS V4 UR1 Refresh, DPM 2022 UR2, or DPM 2025 RTM — install the Private Binaries to resolve the issue described above.

  • If none of the above versions are installed, first update to one of them (e.g., MABS V4 UR1 Refresh or DPM 2025 RTM), and then apply the Private Binaries.

Contact Microsoft Support to obtain private binaries and for any queries.

Issues that are fixed

This update addresses the following issue:

VMDK disk handles were not being closed during backup cancellation. As a result, when the backup snapshot is removed and disk consolidation starts, VMware fails to lock the disks, causing the VM to enter Stun-Cycle or power-off mode.

Note: Installation of the hot fix binaries would require restart of the DMRA service on the MABS server.

Fixed Solution

The DPM/MABS code handling cancellation flows has been updated to properly close VMDK file handles, thus preventing this issue.

How to obtain hotfix

The update packages for Data Protection Manager and Microsoft Azure Backup Server are available on-demand from MABS/DPM Customer Support Services.

Virus-scan claim

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

Hotfix Deployment Steps

The installation process for the binaries differs between MABS and DPM.

​​​​​​​

  1. Download the hotfix zip file from Microsoft Support (DTM link).

  2. Move the zip file to the DPM or MABS server.

  3. Extract the zip file. It will contain two files: DPMRA.exe and DsmFs.dll.

  4. Ensure no backup jobs are running on the DPM/MABS server.

  5. Stop all DPM/MABS services.

  6. Navigate to the appropriate binary path:

    1. MABS: C:\Program Files\Microsoft Azure Backup Server V4\DPM\DPM\Bin

    2. DPM: C:\Program Files\Microsoft System Center <version>\DPM\DPM\Bin (Replace <version> with 2022 or 2025)

  7. Rename the existing binaries:

    • DPMRA.exe → DPMRA_old.exe

    • DsmFs.dll → DsmFs_old.dll

  8. Copy the new DPMRA.exe and DsmFs.dll files into the Bin folder.

  9. Restart the DPM/MABS services.

  10. Confirm that protection jobs resume normally.

  11. Important: A restart of the DMRA service is required after the fix is applied.​​​​​​​

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.