Quantcast
Channel: Backup – Windows and Windows Server forum
Viewing all articles
Browse latest Browse all 1854

Windows 2008 R2 Hyper-V backup fails: VSS error 2155348001

$
0
0

  I have a customer with two Windows 2008 R2 Hyper-V host servers running a wbadmin (Windows Backup).  The one server backs up just fine.  However, the other server consistently fails with the following error:

Detailed error: ERROR - The shared restore point operation failed with error (0x81000101) The creation of a shadow copy has timed out. Try this operation again.

   In the Event Viewer (Application log), I see the following error:

The backup operation that started at '‎2011‎-‎04‎-‎27T06:15:23.955000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

   However I can't find any further error messages (in either the guest VM's event viewer or in the Hyper-V host's event viewer).  

   A few additional notes:

  • Server has SP1 installed.  The problem with the backup predates the SP1 installation.
  • Reboots don't fix the backup problem.
  • After a failed backup, both the Hyper-V VSS writer and the System Writer have the following state in "vssadmin list writers": State: [5] Waiting for completion 
  • I can't do a manual volume or file/folder backup of the drive which has VM's on it using wbadmin because the Volume Shadow fails.
  • A "DELETE SHADOWS ALL" from DISKSHADOW didn't fix the problem.
  • I was wondering if the problem was due to KB982210  (http://garysgambit.blogspot.com/2010/05/windows-2008-hyper-v-vss-backup-bug.html and http://support.microsoft.com/kb/982210).  The HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORAGE\Volume on this system does have a a lot of entries, and the initial logon to the host after a reboot does take a while.  But my Vhdmp.sys has a newer version than this hotfix so I'm assuming that the SP1 for Windows 2008 R2 replaced this file and my guess is that this hotfix won't work on Windows 2008 R2 SP1 servers.  

   Anyone with any good ideas?  [At this point I may even accept bad ones...]


Thanks! dbaddorf


Viewing all articles
Browse latest Browse all 1854

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>