Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Symantec System Recovery 2013 - VSS Snapshot Errors

Created: 11 May 2013 • Updated: 22 May 2013 | 4 comments

We were having a problem backing up a Windows 2008 R2 Standard Server

We kept getting Backup jobs fail with VSS Snapshot errors

The problem was that the system recovery partition did not have VSS provisioned on it.

You can use the vssadmin add shadowstorage to add the shadow storage to any drive that does not have it on already make sure you set the limit to UNBOUNDED

You can use vssadmin list shadowstorage to see if the shadow storage was added correctly

  • Error EC8F17B7: Cannot create recovery points for job: Drive Backup of ESP (*:\), WINRETOOLS (*:\), PBR Image (*:\), OS (C:\).
    Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: VSS_E_INSUFFICIENT_STORAGE (-2147212513).
  • The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: "Unexpected provider error".  Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
    You might see other errors related to VSS Snapshot. A list of VSS Error Codes is available at the following URL:
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa381603(v=vs.85).aspx
  • Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: EndCreateSnapshotSet(-2147212300).
Operating Systems:

Comments 4 CommentsJump to latest comment

Markus Koestler's picture

Have a look here: https://www-secure.symantec.com/connect/forums/ssr-2013-trial-vsseinsufficientstorage-error

*** Please mark thread as solved if you consider this to have answered your question(s) ***

christidevos's picture

Hi we did the same thing by firstly increasing the partition size of the recovery drive with AOMEI Dynamic Disk Manager Server Edition took a few hours this was not needed the above commands fix the issue and even VMWARE migration was possible.

Markus Koestler's picture

If your problem is solved, please ,mark this post as solved.

*** Please mark thread as solved if you consider this to have answered your question(s) ***

Markus Koestler's picture

Please update !

*** Please mark thread as solved if you consider this to have answered your question(s) ***