Since applying security updates to our Hyper-V server (2008R2 Ent. Core), DPM 2010 has been unable to create recovery points of any of the Hyper-V guests.
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried, the error may not reoccur. (0x800423F3))
I also see in the Hyper-V server System event logs:
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 1/18/2011 2:02:02 AM
Event ID: 10111
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: server.lan.com
Description:
Failed to mount the virtual hard disk '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy24\hyper-v...
When I do a vssadmin list writers on the Hyper-V server is shows that the Hyper-V VSS Writer is in a stable state, but it did have a retryable error:
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {de88412e-6663-4486-ac77-3781a8556a5f}
State: [1] Stable
Last error: Retryable error
I tried rebooting our Hyper-V server which cleared the Hyper-V VSS writer 'Retryable error'. But once DPM ran it's scheduled recovery points, the
'Retryable error' returned, same errors as before. I upgraded SQL 2008 to SP2 which updated the Microsoft SQL Server VSS Writer, but that didn’t help either when I attempt to retry a recovery point on one of our Hyper-V guests. I then applied
hotfix KB 2250444 as I was also seeing the MSDPM error (see below) addressed in this hotfix… but the problem still persists.
I am able to use Windows Backup within the Hyper-V guest and create snapshots from Hyper-V, which leads me to believe that this is a DPM issue.
Log Name: Application
Source: MSDPM
Date: 1/19/2011 9:26:26 AM
Event ID: 945
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: server.lan.com
Description:The description for Event ID 945 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
Any ideas would be greatly appreciated.... Thanks!
