DPM Replica is inconsistent : DPM was unable to access the file/folder \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy RRS feed

  • Question

  • Hi,

    I am getting below error message

    The replica of Volume C:\Program Files\Microsoft Azure Backup\DPM\DPM\Volumes\Replica\File System\vol_b3ef1e4a-2c65-48eb-8948-47f09c96e3e5 on server is inconsistent with the protected data source.

    The Operation failed since DPM was unable to access the file/folder \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2178\37e978c8-a8ac-412b-9c68-2d4720623480\

    I Have gone through the discussion forum and found an article to run chkdsk ( to resolve the issue. but while i am running the chkdsk, the issue is not resolved. the path is keep changing e.g now it will show  \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2178\37e978c8-a8ac-412b-9c68-2d4720623480\ path and after chkdsk the path may change to \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3000\37e978c8-a8ac-412b-9c68-2d4720623480\

    kindly suggest



    Wednesday, March 6, 2019 3:22 PM


All replies

  • Hello Vinod,

    Could you give us more details about your environment, version and what you are trying to back up?

    From the information you provided us we can see that you are using Microsoft Azure Backup Server (MABS).

    Also have a look at the MSDPMCurr.errlog for any clues, it's located here by default:
    C:\Program Files\Microsoft Azure Backup Server\DPM\DPM\Temp\MSDPMCurr.errlog

    Best regards,

    Blog: LinkedIn:

    Wednesday, March 6, 2019 4:46 PM
  • Hi Leon,

    Thanks for the time

    You are correct, my Product is MABS Version I was trying to protect the DPM volume (Replica). the path of the affected area is "C:\Program Files\Microsoft Azure Backup\DPM\DPM\Volumes\Replica\File System\vol_b3ef1e4a-2c65-48eb-8948-47f09c96e3e5" and "C:\Program Files\Microsoft Azure Backup\DPM\DPM\Volumes\Replica\File System\vol_3f16db09-8492-4944-b5c2-d1c73a6657a9".

    from the above paths i believe you will get some idea about what i am trying to protect

    I am cross checking the log file which you have said and i will let you know if any clue or solution received.



    Thursday, March 7, 2019 8:18 AM
  • It appears that you are using quite an old version of MABS (v1), I would first of all suggest you to update MABS to the latest version to see if it resolves the issues.

    The latest version is MABS v3:

    Microsoft® Azure Backup Server v3 (13.0.415.0)

    Blog: LinkedIn:

    • Marked as answer by Vinod C V Friday, March 29, 2019 4:18 PM
    Thursday, March 7, 2019 1:55 PM