Answered by:
Failed Backups - unable to create volume snapshot

Question
-
I've been running WHS for several months and have not been able to backup one XP Pro machine (out of 5 that work just fine, even a Vista Business notebook).
I always get the same error "The backup failed because your computer was unable to create a volume shapshot. To resolve this problem, try running "chkdsk /f /r" on each of your hard drives and restart your computer".
I get the same error when trying to backup any portion of the 2 drives on the machine. I have run chkdsk many times and get no errors. I have reformated one of the drives twice and still no luck.
I have updated all software to the latest on both the WHS and XP Pro machines (updated both today). I have stopped my firewall and virus software - no change.
The machine works just fine woth all MS software (word, PP Excel, outlook ...).
Any Ideas??
Thanks, Paul
Monday, September 1, 2008 9:44 PM
Answers
-
Paul, your errors make me suspicious of the state of that computer.In addition to Colin's questions, have you ever had disk problems? Cloned a drive in it? Do you install/uninstall software on it regularly? How long has it been since you last reinstalled Windows (or last restored it to factory state, if from an OEM like Dell)? How old is it?
I'm not on the WHS team, I just post a lot. :)- Proposed as answer by jamesf3 Thursday, December 4, 2008 9:40 PM
- Marked as answer by Lara JonesModerator Wednesday, May 13, 2009 7:02 PM
Friday, September 5, 2008 10:38 PMModerator
All replies
-
You may find this blog post of use. You will want to perform those steps on the PC having the issue.Monday, September 1, 2008 10:17 PMModerator
-
Ken, Thanks for the possible solution. Unfortunately it did not work.
I got the following 4 errors:
The volume shadow service is not started.
The MS software shadow copy provider service is not started
vss_ps.dll is not an executable file and no registration helper is registered for this file type
LoadLibrary ("vssui.dll") failed. The specified module could not be found.
Any other ideas?
Thanks, Paul
Friday, September 5, 2008 6:07 PM -
Paul,
What does the logs on the Client show? They are available at:
%SystemDrive%\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs.
It might give some indication.
Also, have you ever used any other form of backup/cloning software on that particular computer, as some programs such as Acronis interfere with the VSS service.
Colin
If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.Friday, September 5, 2008 6:26 PMModerator -
Paul, your errors make me suspicious of the state of that computer.In addition to Colin's questions, have you ever had disk problems? Cloned a drive in it? Do you install/uninstall software on it regularly? How long has it been since you last reinstalled Windows (or last restored it to factory state, if from an OEM like Dell)? How old is it?
I'm not on the WHS team, I just post a lot. :)- Proposed as answer by jamesf3 Thursday, December 4, 2008 9:40 PM
- Marked as answer by Lara JonesModerator Wednesday, May 13, 2009 7:02 PM
Friday, September 5, 2008 10:38 PMModerator -
After 6-8 hours of fighting this, using all the various ideas from many forum posts, for me the solution was simply to remove registry remnants after a control panel uninstall of StorageCraft's ShadowProtect. One of the vssadmin List commands showed ShadowProtect was still active after the "uninstall".
Others have posted that various imaging or backup programs might mess with VSS. So true in this case.
Here's their removal post: http://forum.storagecraft.com/Community/forums/p/683/3092.aspx
I hope others find this post and pursue similar fixes if appropriate.
Jim
Thursday, December 4, 2008 9:48 PM -
Hi I am not sure if you are still looking for an answer to your problem, but I have experienced the very same problem and have just managed to fix it without changing anything in the registry.
try the following
1. open the WHS console
2. go to Computers and Backups
3. go to Configure Backups
4. if your problem is the same as mine, you will see a dialogue box with a few checked boxes. uncheck every box except the drive(s) you want to backup
5. press OK
6. start backup manually
this should work,
in my case, i have a hidden drive that is not formatted in NTFS which cannot be backuped. once i unchecked the box for the hidden drive, WHS backup works perfectly
good luck
paul from torontoSaturday, March 28, 2009 10:51 PM -
I'm having this issue also. The last successful backup that completed shows my 2 drives backed up:
Name Status
C: (Local Disk) Complete
D: (Samsung_HD753LJ) Complete
Now, for all unsuccessful automated and manual backups, I see this:
Name Status
(Local Disk) Failed
C: (Local Disk) Complete
It seems the D drive isn't being seen properly. I have run chkdsk with no flags, with /f and with /f /r on both drives and this has not helped. Running chkdsk without any options states that there is an error in stage 2 of 3, but when I run /f and /f /r, it completes with no errors reported.
I'm using the HP Mediasmart EX485 and this issue was happening before and still after installing the HP Update 2.5 that just came out.
I checked Services and Volume Shadow Copy is running, I've also tried restarting it a few times too.
Oddly enough my drive also disappeared from explorer in Vista completely when this started happening, and took a few reboots, but it came back. I can still read and write from/to the D: Drive and was hoping chkdsk would have solved any issues with it otherwise.
I thought it was the same issue as Paul mentioned above since I did have an ESATA drive on that might have confused the backup configuration but I reconfigured it with the external ESATA drive off... no change, still fails the backup.
Another computer on the network is being successfully backed up daily/automatically.Saturday, April 25, 2009 8:58 AM -
I'm having this issue also. The last successful backup that completed shows my 2 drives backed up:
Name Status
C: (Local Disk) Complete
D: (Samsung_HD753LJ) Complete
Now, for all unsuccessful automated and manual backups, I see this:
Name Status
(Local Disk) Failed
C: (Local Disk) Complete
It seems the D drive isn't being seen properly. I have run chkdsk with no flags, with /f and with /f /r on both drives and this has not helped. Running chkdsk without any options states that there is an error in stage 2 of 3, but when I run /f and /f /r, it completes with no errors reported.
I'm using the HP Mediasmart EX485 and this issue was happening before and still after installing the HP Update 2.5 that just came out.
I checked Services and Volume Shadow Copy is running, I've also tried restarting it a few times too.
Oddly enough my drive also disappeared from explorer in Vista completely when this started happening, and took a few reboots, but it came back. I can still read and write from/to the D: Drive and was hoping chkdsk would have solved any issues with it otherwise.
I thought it was the same issue as Paul mentioned above since I did have an ESATA drive on that might have confused the backup configuration but I reconfigured it with the external ESATA drive off... no change, still fails the backup.
Another computer on the network is being successfully backed up daily/automatically.
Hi,
I'm working through the forums for the monthly reports and I just caught this thread.
If the drive goes missing from explorer, this will interfere with backups as backup places a load on the drive. Please check for updated storage drivers for the PC in question. Also, do you have any DVD burning or backup software installed on this machine?
Thanks!
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerWednesday, May 13, 2009 7:06 PMModerator -
I had the same Windows Home Server backup issue on one of my systems running Windows Vista (and later on Windows 7 RC1). Nothing I found in any of the related forum posts helped.
After taking a closer look at the installed VSS components on the problematic system using 'vssadmin', it turned out that there seemed to be a "leftover" VSS provider from a previous (properly uninstalled) Norton Ghost. That's at least the only somewhat plausible explanation I can come up with.
First, take a look at the providers in the system:
C:\Windows\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.Provider name: 'Symantec Software VSS Provider'
Provider type: Software
Provider Id: {262b716e-bb23-41b5-aaef-e2c15e767167}
Version: 1.0Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7The 'Symantec Software VSS Provider' was suspicious. So, I simply went into regedit, searched for its name, and removed the two related provider entries.
Another 'vssadmin list providers' confirmed that the Symantec provider entry was indeed gone:
C:\Windows\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7After that, my Windows Home Server backups worked like a charm again. I am not saying that you will see the same Symantec VSS provider, however, my point is that it probably does not hurt to take a peek at your providers, and see if there is anything questionable to be seen.
- Proposed as answer by FourHumboldt Wednesday, June 3, 2009 5:34 AM
Wednesday, June 3, 2009 5:34 AM -
hi guya,
almost the same problem.
the pc in question is a ghosted image with a different key and the hard ware is about 1-1.5 months older. same cpu, same hard drives and all. one has the problem and the other does not.
the one that come up with the back up error. i can do a back up from the pc, and from the network. ( a manual backup ) but when the timer on the server comes on and says to the network time for a backup. it does not and says the " can not do a snapshot ". ok done chkdsk, done the reg hack, even went and turned off the save power on the nic card, wich WHS wants to turn on by defualt.
a error showed up this morring in the event log on the pc. it was can not do a shadow copy because of the free space.
like i said 2 pc's and one waork and this one does not.
the drive in questiopn is a 1tb drive. it has 685 gb free space.
when and looked at the application events and about 30 min after the back up was ended by the server this showed up.
Event Type: Error
Event Source: HomeServer
Event Category: HomeBackup
Event ID: 770
Date: 6/6/2009
Time: 4:21:52 AM
User: N/A
Computer: my-home-pc
Description:
Backup set 13 on my-home-pc failed: Microsoft.HomeServer.Backup.VSS.ShadowVolumeException: Exception from HRESULT: 0x80042308 ---> System.Runtime.InteropServices.COMException (0x80042308): Exception from HRESULT: 0x80042308
at Microsoft.HomeServer.Backup.VSS.IVssBackupComponents.GetSnapshotProperties(Guid SnapshotId)
at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
--- End of inner exception stack trace ---
at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet..ctor(VolumeInfo[] volumes)
at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()
got any ideas. i am out of them.
thank you
Sunday, June 7, 2009 2:35 AM -
hi guya,
almost the same problem.
the pc in question is a ghosted image with a different key and the hard ware is about 1-1.5 months older. same cpu, same hard drives and all. one has the problem and the other does not.
the one that come up with the back up error. i can do a back up from the pc, and from the network. ( a manual backup ) but when the timer on the server comes on and says to the network time for a backup. it does not and says the " can not do a snapshot ". ok done chkdsk, done the reg hack, even went and turned off the save power on the nic card, wich WHS wants to turn on by defualt.
a error showed up this morring in the event log on the pc. it was can not do a shadow copy because of the free space.
like i said 2 pc's and one waork and this one does not.
the drive in questiopn is a 1tb drive. it has 685 gb free space.
when and looked at the application events and about 30 min after the back up was ended by the server this showed up.
Event Type: Error
Event Source: HomeServer
Event Category: HomeBackup
Event ID: 770
Date: 6/6/2009
Time: 4:21:52 AM
User: N/A
Computer: my-home-pc
Description:
Backup set 13 on my-home-pc failed: Microsoft.HomeServer.Backup.VSS.ShadowVolumeException: Exception from HRESULT: 0x80042308 ---> System.Runtime.InteropServices.COMException (0x80042308): Exception from HRESULT: 0x80042308
at Microsoft.HomeServer.Backup.VSS.IVssBackupComponents.GetSnapshotProperties(Guid SnapshotId)
at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
--- End of inner exception stack trace ---
at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet.CreateShadowVolume(VolumeInfo[] volumes)
at Microsoft.HomeServer.Backup.VSS.ShadowVolumeSet..ctor(VolumeInfo[] volumes)
at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()
got any ideas. i am out of them.
thank you
You would probably get a better response if you started your own thread (instead of adding to one that's already marked as answered). Having said that, try running vssadmin list providers and vssadmin list writers from a command prompt and post the results.Sunday, June 7, 2009 1:59 PMModerator -
I'm guessing you've long since resolved your problem and moved on - I've just recently been battling this one and have had the "...backup failed.. unable to create volume snapshot..." I currently back-up 4 machines to my homeserver (3 of which are very stable/successful back-ups for over a year). Alas, my 4th machine, the most complex of the 4 (Vista 64bit, SLI, 4 hard drives, etc) seemed to work intermittently, at best. Auto back-ups routinely failed and ultimately, the manual back-ups failed as well. I'm always tweaking this machine and couldn't think of anything that might account for the problems. Hardware is all healthy, but none-the-less tried the suggestion to run chkdsk /f /r. Similar to what others have said, it didn't have an impact for me. I tried uninstalling/re-installing HS Connector, turned SLI on/off, etc. No joy.
Anyway several forum entries mentioned registering a series of .dll's related to VSS - which I started to do and then part of the way down the list one dll partially loaded and the remainder failed in one way or another.
To cut to the chase, I went to Windows System Configuration on this machine and found the system configured to do a Selective Startup - so, some services were getting by-passed. I changed to "Normal startup" and applied and restarted. I reinstalled HS Connector and the back-ups are running once again. My "best guess" is there may have been some dependent services that were not running and configuring to do a Normal startup seems to have restored functionality.Saturday, October 10, 2009 4:44 AM -
Hi EEWdad
well as i was toald , i when and made a new tread. but yes the fight still goes on.
let me find that thread and post it for you. here
http://social.microsoft.com/Forums/en-US/whssoftware/thread/4b53d4f2-7841-477d-8169-986b48fff91d
i do not know if there is a newer one or notSunday, October 11, 2009 10:15 PM -
After writing this - dang if I didn't encounter the problem again. This time I noticed it was after I updated a couple of drivers.
I use ParetoLogic DriverCure to keep tabs on driver updates and usually do update when new drivers are available. After updating, the back-up failed again. So, I uninstalled the connector; however I noticed that a folder was left on the C:\ (Programs\Windows Home Server ). I deleted that and ran a registry cleaner to tidy-up any loose ends. After re-starting the machine I reinstalled the connector application and it has been running well once again.
I think Homeserver keeps tabs on drivers and may not handle [some] driver updates well(?). Going forward, if I need to update a driver, I will probably uninstall the HS Connector, delete the C:\ Programs \HS folder, update the driver and then reinstall the HS Connector.
I'll be upgrading to Win 7 on this machine soon - I'll keep my fingers crossed the issue goes away entirely with the new OS!
Dell XPS 720-H2C
Intel QX-6850 @3.33Ghz
2x EVGA GTX-260 Core 216 - SLI
4GB RAM / ~ 2TB onboard disc storage
Vista Ultimate - 64bit- Proposed as answer by althefirst Tuesday, November 3, 2009 1:57 PM
Tuesday, November 3, 2009 1:03 PM -
well after chasing this problem around for 6 months. this is what i did.
some were i had read that the server wanted to have disk clusters at 4 mb per. i then copyed the hard drive to a new drive.
i had done this once before but this time i formated the drive to the 4 mb size. then copyed the data back.
i have not had a problem for 14 days. if it was broken still it would have showed up by now.Tuesday, November 3, 2009 2:02 PM -
Had similar problem. go to command prompt and run these commands.
net stop vss
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dllThis should fix the problem.
Friday, June 3, 2011 2:53 PM -
Had same problem. To fix this problem run these commands in command prompt.
net stop vss
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll- Proposed as answer by Dark Elf Friday, June 3, 2011 2:55 PM
Friday, June 3, 2011 2:55 PM -
I just wanted to add that none of these suggestions worked for me, however I did find something that did work.
I'm running Windows 7 x64 SP1.
First, my situation was a hard drive upgrade. I've done this several times, and this is the first time I've run into this issue.
Anyhow, I ran chkdsk several times.
I ran the re-registration above several times (which failed, so I used a long list from this post which got everything re-registered - put it in a BAT file and run it):
Backup Failures in Server 2008
But that still didn't fix it.
So, I finally had this other idea...
I ran Windows Backup in Windows 7 whch uses the same VSS infrastructure and backed up the machine to an external drive.
After that backup succeeded, Windows Home Server was able to back up my machine again.
- Edited by greggerca2 Monday, February 20, 2012 11:51 PM Fixed link
Monday, February 20, 2012 11:50 PM