Solution: Error ID 958 and Internal error code 0x80990A9E performing Item Level Recovery in DPM 2010 - System Center: Data Protection Manager Engineering Team Blog - Site Home - TechNet Blogs

Solution: Error ID 958 and Internal error code 0x80990A9E performing Item Level Recovery in DPM 2010

Solution: Error ID 958 and Internal error code 0x80990A9E performing Item Level Recovery in DPM 2010

  • Comments 1
  • Likes

ToolsWhen you try to perform Item Level Recovery (ILR) in System Center Data Protection Manager 2010, you may get the following pop-up message:

DPM cannot browse the contents of the virtual machine on the protected computer <name>. Item level recovery is not supported in the following scenarios.
1. The VHD contains a dynamic disk inside the guest OS.
2. The VHD has no volume.
3. HyperV role is not installed on DPM server.

Please perform a full restore of the virtual machine.

ID: 958
Details: Internal error code: 0x80990A9E

image

The error is pretty explicit as to the cause of the issue, but what if you're seeing this because the Hyper-V role isn't installed, and the reason it's not installed is because the DPM Server is installed in a Virtual Machine? 

When DPM 2010 performs an item level recovery, it actually mounts the VHD from the backup as a mountable file system on the DPM server itself.  Unfortunately, Windows Server 2008 (inside a guest) does not provide a way to mount a VHD if you are actually in a VM already, so a virtualized DPM server can’t mount the volume – hence the error.

Fortunately there is a workaround we can use, which is to restore the .VHD as a file then mount it manually using Windows Server 2008 R2 disk management.  From there you can browse the contents of the .vhd file system and manually restore your files.

Hope this helps,

J.C. Hornbeck | System Center Knowledge Engineer

clip_image001 clip_image002

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • This is the way that we have been doing it as well, but unfortunately this is a time consuming way to recover data (recovering a LOT of data and using very little of it).  While local restores happen quickly (recovering directly to the DPM server), this doesn't scale very far in the real world.  Any idea when a fix will be available?  This is really the only thing keeping us from migrating full scale to DPM 2010.  Thanks!