Video Screencast Help

Upgraded from BESR 2010 to SSR 2013 - backups failing with VSS error

Created: 12 Apr 2013 | 6 comments
asolmssen's picture

Hi all,

I have a Windows 7 x64 SP1 workstation that was happily running BESR 2010 Desktop to do backups to an external 3TB disk. This is my personal workstation. I got the bright idea to upgrade to SSR 2013 as a guinea pig machine for my other ones out there. This has not gone well.

Upgrade was in-place - Installer detected BESR 2010 and removed it then installed 2013. I rebooted, and since then have rebooted many times. Backups fail with this event in the SSR log:

 

Error EC8F17B7: Cannot create recovery points for job: Backup of 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). (UMI:V-281-3215-6071)
 
Details: 
Source: Symantec System Recovery
 
System boots from a 120GB SSD with about 30GB free, and has a 1TB data volume that is two 1TB WD RE3 drives running Intel RST hardware mirroring. There are two jobs - one backs up the System Reserved and C: drives, the other backs up the G: data volume, running at 4AM and 5AM respectively.

After a reboot, VSS shows:

 

C:\Windows\system32>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {eb4de408-2901-4f0e-a597-da0b6e07860e}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {cde03ce4-0883-4b6a-90b8-382c6a461aac}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {4b622621-34f1-405a-9dcf-1293833541b7}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c1b60f1c-cb56-4dc6-a9a0-c4813527beec}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {55f45e21-8b25-4864-9eb7-bac68c72bd00}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {aaa41c57-8d08-4d35-ad3f-f48d77857fe3}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f6fde25a-021a-4123-b0fe-b997bdbb0bf4}
   State: [1] Stable
   Last error: No error
Following the backup attempt:
 
C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {eb4de408-2901-4f0e-a597-da0b6e07860e}
   State: [7] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {c98aa249-41e9-469b-9a03-324216609b11}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {cde03ce4-0883-4b6a-90b8-382c6a461aac}
   State: [7] Failed
   Last error: Timed out

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {edc25c42-7faf-4c7d-8404-96107164bd97}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {78950130-6c85-48a2-b54f-c83da4277f48}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {fb7d27d5-27c1-4f8d-a128-829a720f7fe9}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {7dc0a632-1b52-4605-a034-2583adfdc773}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {aaa41c57-8d08-4d35-ad3f-f48d77857fe3}
   State: [7] Failed
   Last error: Timed out
And the following errors show up in the Application log:
 
Log Name:      Application
Source:        VSS
Date:          4/12/2013 1:50:52 PM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      BITBOY-i7
Description:
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetAsrMetadata.  hr = 0x80070001, Incorrect function.
 
Operation:
   PrepareForBackup event
 
Context:
   Execution Context: ASR Writer
   Execution Context: Writer
   Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Name: ASR Writer
   Writer Instance ID: {320def6b-f19f-4aa2-8c77-6642f6a185be}
 
Error-specific details:
   ASR Writer: Incorrect function. (0x80070001)
 

 

Log Name:      Application
Source:        Symantec System Recovery
Date:          4/12/2013 1:51:04 PM
Event ID:      100
Task Category: High Priority
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      BITBOY-i7
Description:
Error EC8F17B7: Cannot create recovery points for job: Backup of 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). (UMI:V-281-3215-6071)
 
Details: 
Source: Symantec System Recovery
 
 
I'd like to get this working again - any thoughts about what I need to do here? My instinct is to uninstall and reinstall 2013, but I feel like there may be some 2010 stuff left somewhere that's causing this. Or if I'm wrong, let me know - looking forward to some guidance.
 
Best,
 
---- Andrew Solmssen
Operating Systems:

Comments 6 CommentsJump to latest comment

Chris Riley's picture

There are two jobs - one backs up the System Reserved and C: drives, the other backs up the G: data volume, running at 4AM and 5AM respectively.

Which job fails with the VSS_E_INSUFFICIENT_STORAGE error?

I ask because I am working with a customer who is only seeing this issue when backing up the system reserved partition.

asolmssen's picture

I think I figured it out. The VSS_E_INSUFFICIENT_STORAGE error was coming from the first job, the one that includes the System Reserved partition. I was able to resolve this by:

assigning a drive letter to the System Reserved partition in Disk Management.

going to an elevated command prompt and issuing this command:

FSUTIL USN DELETEJOURNAL /N /D X:

where X is the letter I assigned to the System Reserved partition above.

I then removed the drive letter using Disk Managment, and was able to complete a run of that job in SSR 2013.

One symptom of this was that size of files + free space was less than 50MB of the actual 100MB in that partition.

SSR did a full image instead of incremental, even though I requested an incremental from Run Backup With Options.

Will try the other job as soon as this is done.

UPDATE:

Resolving the System Reserved partition issue allows the second job to run as well. It also did a full backup, not an incremental.

 

 

asolmssen's picture

incremental backups on the large data drive are failing again with this error:

 

 
-Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: EndCreateSnapshotSet (-2147212302).
 
(UMI:V-281-1267-14)
 
a check of the application log shows no underlying VSS error - just the error from SSR.
 
UPDATE - Resolved. Increasing the Shadow Copy storage area on the affected volume from 1% to 5% appears to have resolved this and has let me complete an incremental.
 
PravinAmin's picture

Hi,

Please refer to technote:http://www.symantec.com/docs/TECH200584  and see if the issue is resolved.

 

-Thanks,

Pravin

inn_kam's picture

 As mentioned by Pravin in technote http://www.symantec.com/docs/TECH200584 

u mentioned that windows is 7 then 

check

  • Ensure that the Microsoft VSS services are not 'disabled'. Manually start VSS, This should start without any errors. 
  • Ensure that all VSS writers are in stable state condition. Do this by opening a command prompt with administrative permissions. At the prompt, type VSSADMIN LIST WRITERS. All writers should be stable. 
  • Ensure that the various Application VSS Writer services can be started in the services console without any errors.
asolmssen's picture

As noted in my post above, the solution was to up the amount of Shadow Copy storage space on the large volume. Thanks!