Vidéos d'aide de Screencast
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

VSS Errors on server 2008r2 DC (backup server)

Created: 21 Fév. 2013 | 5 comments

I have a client who's backup is failing with the below on DC6 (backup server)

Backup - Snapshot Technology: Initialization failure on: "\\STV-DC6.service-line.local\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
 
V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
 
 
Please see below but I wondered if anyone has any ideas to progress this?  The server has been rebooted.  I have tried specifying the microsoft advanced open file instaad of automatically selecting the technology.
 
 
 
 
Event log errors relating to vss
-------
 
I have installed all of the latest symantec updates and rebooted the server.  The event log shows the below:
 
Log Name:      Application
Source:        VSS
Date:          21/02/2013 08:11:07
Event ID:      12293
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      STV-DC6.service-line.local
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({261b5483-21f2-40d0-bd7d-41a13c1c9bf4}) [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
]. 
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">12293</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-02-21T08:11:07.000000000Z" />
    <EventRecordID>29027</EventRecordID>
    <Channel>Application</Channel>
    <Computer>STV-DC6.service-line.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data>
    <Data>EndPrepareSnapshots({261b5483-21f2-40d0-bd7d-41a13c1c9bf4})</Data>
    <Data>0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
</Data>
    <Data>
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet</Data>
    <Binary>2D20436F64653A20434F52534E50534330303030313632342D2043616C6C3A20434F52534E50534330303030313630352D205049443A202030303030353930382D205449443A202030303030383132382D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>
 
----------
 
vssadmin list writers displays the below:
 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Waiting for responses.
These may be delayed if a shadow copy is being prepared.
 
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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {a9d02d9c-1b0f-4c5e-92d3-91a957466520}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {f3aa9ddd-0ec4-43c4-8236-756aac46819b}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {458b444e-c971-4631-a580-e69d5595f0d8}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {f90e6d1e-82af-460e-9486-aa83dd1d54fa}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {ed99dbcc-e316-433a-bd5a-8376fd80d6ba}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {d452c962-570d-4446-8217-d24e25fd7c79}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {11e14f66-9f97-41e7-9ae4-8da61df4c573}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {27adfc78-fb3c-45e0-a15b-0e9727bca1d8}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {206476f3-f08e-4e84-b681-0fdd645fcd97}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {845652c6-3545-47d2-a6a6-5b65e2053aa5}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {75b4caf3-8065-4d68-85a2-43b9c5487823}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {d4fc7552-5e10-4cef-8166-013697b02748}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {3c62b8d3-e76f-49ba-a53d-619a77566fcf}
   State: [7] Failed
   Last error: Timed out
 
 
 
 
Operating Systems:

Commentaires CommentairesAccéder au dernier commentaire

l'image des CraigV

Hi,

No need to run "vssadmin list writers" as it clearly shows the writers are not stable.

A server restart will fix this. Once done, open a command prompt and run: vssadmin list writers. They should all be stable and running, and if so, run the backup again. Report back with an update.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

l'image des anthony.richardson83

Hi there

I have already tried a reboot which usually fixes this but on this occasion it hasn't.

thanks

Anthony

l'image des CraigV

Anthony: Here's a pretty good TN on how to go about this:

http://www.symantec.com/business/support/index?pag...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

l'image des anthony.richardson83

We are still having issues.  It is a 2008r2 server and not 2003 so the hotfix is not available?  I have also read re-registering the dll files is not recommended.  The writers are still listing as failed.

l'image des CraigV

...if this is Windows Server 2003 do a Google search for the VSS ROllup Patch. Check for the latest as this fixes VSS errors in this particular OS.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...