DPM failed to access the volume \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy53\ RRS feed

  • General discussion

  • Hi All,

    We are using DMP 2012 R2 (Version 4.2.1533.0). I am getting below error due to which backup is getting failed, every time replica is getting inconsistent. I have reconfigured backup/done Consistency Checks several times but issue still exist. I need help to resolve this issue. I am facing this issue for particular server only all, other servers from same protection groups are in OK state.

    Type: Consistency check
    Status: Failed
    Description: DPM failed to access the volume \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy53\ on ServerFQDN,com. This could be due to
    1) Cluster failover during backup or
    2) Inadequate disk space on the volume.
     (ID 2040 Details: The device is not ready (0x80070015))
    More information
    End time: 1/24/2019 7:34:18 AM
    Start time: 1/24/2019 2:00:05 AM
    Time elapsed: 05:34:12
    Data transferred: 494,407.45 MB
    Cluster node -
    Source details: H:\
    Protection group members: 1
    Protection group: XXXXXX
    Items scanned: 171
    Items fixed: 15
    • Edited by SangramR Friday, January 25, 2019 1:20 PM
    Friday, January 25, 2019 1:16 PM

All replies

  • Hello!

    It looks like the shadow copy was deleted before the job finished, check the System event and look for any errors from volsnap.

    Here are two (2) reasons that are the most likely ones for this error:

    1. The shadow copy file could not grow in time.

    2. There was not enough free disk space to grow the shadow copy.

    Here's what you should check:

    1. Make sure there is sufficient free space on the H: drive.
    2. Run a NTFS Defrag to consolidate free space.
    3. Move the shadow copy space to another volume that is not as heavily used and / or has more free space.

    A quick fix that also works with many things would be to stop the protection of this server with the retain data option, and then re-add the server.

    Best regards,

    Blog: LinkedIn:

    Friday, January 25, 2019 2:15 PM
  • Hi,

    Thanks for your reply and sorry for my delayed response.

    I removed folders and re-added in backup, post that backup was done successfully. Also i can see 3 days ago date as oldest recovery Point, I though my issue is resolved now but today morning I get different error i.e. "Recovery Point Creation Failed". The Issue Description is same as above.

    Total space in H: is 2.92TB, in which the folder of which we are taking backup is 1.01 TB in size and available free space is 1.18 TB.

    I have found event Id 25 related to VOLSNAP which is stating that "The shadow copies of volume H: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."

    PFB list of shadow storage.

    C:\Windows\system32>vssadmin list shadowstorage
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{88b1ae0d-cb77-11e5-80c7-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{88b1ae0d-cb77-11e5-80c7-806e6f6e69
       Used Shadow Copy Storage space: 53.6 MB (0%)
       Allocated Shadow Copy Storage space: 640 MB (0%)
       Maximum Shadow Copy Storage space: 12.7 GB (10%)

    Shadow Copy Storage association
       For volume: (H:)\\?\Volume{9b7ece95-5116-45a3-a5a4-315425ef6d2c}\
       Shadow Copy Storage volume: (H:)\\?\Volume{9b7ece95-5116-45a3-a5a4-315425ef6d
       Used Shadow Copy Storage space: 721 MB (0%)
       Allocated Shadow Copy Storage space: 2.93 GB (0%)
       Maximum Shadow Copy Storage space: 300 GB (9%)

    Tuesday, January 29, 2019 11:51 AM
  • You will either have to do the following:

    • Free up some more disk space.
    • Take the backup at a time when there are no changes to the files during backup.
    • Change the Shadow Copy Storage space to use a different drive that has more free space.

    The Volume Shadow Copy (VSS) has to maintain the snapshot by copying changed file blocks to the snapshot file for the duration of the backup. 

    Blog: LinkedIn:

    Tuesday, January 29, 2019 1:25 PM
  • Dear Leon,

    Thanks for your reply.


    Today backup has been completed successfully, also I can see the latest recovery point.

    I will keep it under observation for this whole week and will update you with the status.

    I haven't performed above suggested steps yet, till now i have done only backup reconfiguration.

    Thanks once again.

    Wednesday, January 30, 2019 6:53 AM
  • Okay great to hear that it’s working well so far! Keep us updated, the removal / readding might have been to some aid perhaps!

    Blog: LinkedIn:

    Wednesday, January 30, 2019 6:57 AM
  • Hello,

    I wanted to check in to see if you have any update?

    Blog: LinkedIn:

    Wednesday, March 6, 2019 3:50 PM
  • Hi Leon,

    Till now DPM is working without any issue.

    Thank you so much for your help.

    Wednesday, March 27, 2019 9:35 AM
  • That is good news, then I suggest we close this thread, you may change this thread type to a Question and then you can mark as answer the reply that you found helpful!

    Blog: LinkedIn:

    • Edited by Leon Laude Wednesday, March 27, 2019 9:55 AM
    Wednesday, March 27, 2019 9:40 AM