locked
DPM encountered an error while reading from the recovery point used for recovery. RRS feed

  • Question

  • Hi Guys I'm getting this error:

    DPM encountered an error while reading from the recovery point used for recovery. Either the recovery point no longer exists or, if you selected a share for recovery, the path to its contents is missing from the recovery point.  (265)

    The DPM Server is on Windows 2012 DPM is 2012R2 4.2.1273.0

    The Server being backed up is 2012 R2 with DPM Agent 4.2.1273.0

    The Server has 3 Data Volumes (C: Drive) and D and E its the D and E drive that i get this error if i try and recover data from DPM.  the C Drive is fine.  the D and E Drive are different in that 1 De-dupe is enabled and 2 the Shadow Copies for these Volumes are stored on separate Disks F and G respectively.

    I've removed the Protection from drives D and E and reinstated it but every recovery point created brings up the same error message. I'm not sure where to go next do I need to Protect the Disks that have the Shadow copies on also? Many thanks in advance Gordon.

    Tuesday, April 28, 2015 4:06 PM

Answers

  • Hi,

    It seems you are in a configuration where the Windows 2012 based DPM server does not understand how to read Windows 2012 R2 Dedup data structure which is what the DPM replica volume is.

    See the DPM supported and unsupported scenarios here under the deduplication issues section. 

    We have a fix in DPM2012 R2 UR5 that will protect the Windows 2012 R2 dedup volume in a non-dedup state on the DPM Server, but unfortunately that will not allow previous recovery points to be read.

    KB3021791-Description of Update Rollup 5 for System Center 2012 R2 Data Protection Manager

    Backup job for dedupe-enabled volume on Windows 2012 R2 fails. For example, Data Protection Manager backup might fail for following setup:
    • Data Protection Manager2012 R2 is installed on Windows Server 2012.
    • Data Protection Manager is protecting a dedupe-enabled volume on Windows Server 2012 R2.

    This also applied to restores as the above was for D2D2T backup that may fail as it needs to read the recovery point to back it up to tape.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Tuesday, April 28, 2015 10:23 PM

All replies

  • Hi,

    It seems you are in a configuration where the Windows 2012 based DPM server does not understand how to read Windows 2012 R2 Dedup data structure which is what the DPM replica volume is.

    See the DPM supported and unsupported scenarios here under the deduplication issues section. 

    We have a fix in DPM2012 R2 UR5 that will protect the Windows 2012 R2 dedup volume in a non-dedup state on the DPM Server, but unfortunately that will not allow previous recovery points to be read.

    KB3021791-Description of Update Rollup 5 for System Center 2012 R2 Data Protection Manager

    Backup job for dedupe-enabled volume on Windows 2012 R2 fails. For example, Data Protection Manager backup might fail for following setup:
    • Data Protection Manager2012 R2 is installed on Windows Server 2012.
    • Data Protection Manager is protecting a dedupe-enabled volume on Windows Server 2012 R2.

    This also applied to restores as the above was for D2D2T backup that may fail as it needs to read the recovery point to back it up to tape.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Tuesday, April 28, 2015 10:23 PM
  • Super thanks, I have updated DPM to UR6 this morning and will try and update the Agent on the server tomorrow evening :) as reboot required - hopefully then it will work.
    Wednesday, April 29, 2015 8:53 AM
  • That's worked thanks... even with out updating the Agent :)
    Friday, May 1, 2015 8:43 AM