Could not create systemstatebackup on Windows 2008 DC
we have issues system state backup after upgrading member server (win 2008 standard) domain controller.
our domain windows server 2003 functional level 1 dc server running win 2003 sp2 , 2 servers runnig running win 2008 sp1.
on both 2008 server there same issue "system writer not found in backup.".
example:
~~~~~~~
c:\windows\system32>wbadmin start systemstatebackup -backuptarget: -quiet
wbadmin 1.0 - backup command-line tool
(c) copyright 2004 microsoft corp.
starting system state backup [28.4.2008 17:34]
retrieving volume information...
this backup system state volume(s) local disk(c d:.
creating shadow copy of volumes requested backup.
creating shadow copy of volumes requested backup.
summary of backup:
------------------
backup of system state failed [28.4.2008 17:34]
log of files backed up
'c:\windows\logs\windowsserverbackup\systemstatebackup 28-04-2008 17-34-31.log'
log of files backup failed
'c:\windows\logs\windowsserverbackup\systemstatebackup_error 28-04-2008 17-34-31.log'
system writer not found in backup.
~~~~~~~
application event log displays these 2 errors after 2008 system restart:
1.
log name: application
source: vss
date: 28.4.2008 16:17:03
event id: 12289
task category: none
level: error
keywords: classic
user: n/a
computer: *
description:
volume shadow copy service error: unexpected error netgroupgetusers(). hr = 0x80070005.
operation:
initializing writer
context:
writer class id: {e8132975-6f93-4464-a53e-1050253ae220}
writer name: system writer
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<system>
<provider name="vss" />
<eventid qualifiers="0">12289</eventid>
<level>2</level>
<task>0</task>
<keywords>0x80000000000000</keywords>
<timecreated systemtime="2008-04-28t14:17:03.000z" />
<eventrecordid>1017</eventrecordid>
<channel>application</channel>
<computer>*</computer>
<security />
</system>
<eventdata>
<data>netgroupgetusers()</data>
<data>0x80070005</data>
<data>
operation:
initializing writer
context:
writer class id: {e8132975-6f93-4464-a53e-1050253ae220}
writer name: system writer</data>
<binary>2d20436f64653a20534543534543524330303030323433392d2043616c6c3a20534543534543524330303030323333302d205049443a202030303030313232342d205449443a202030303
030313735362d20434d443a2020433a5c57696e646f77735c73797374656d33325c737663686f73742e657865202d6b204e6574776f726b53657276696365202020202020202d20557365723a204e
5420415554484f524954595c4e4554574f524b2053455256494345202020202d205369643a2020532d312d352d32302d204572726f723a4e657447726f75704765745573657273282920202020202
0</binary>
</eventdata>
</event>
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
2.
log name: application
source: microsoft-windows-capi2
date: 28.4.2008 16:17:03
event id: 512
task category: none
level: error
keywords: classic
user: n/a
computer: *
description:
the cryptographic services service failed initialize vss backup "system writer" object.
details:
system writer object failed initialize vss.
system error:
catastrophic failure
.
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<system>
<provider name="microsoft-windows-capi2" guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" eventsourcename="microsoft-windows-capi2" />
<eventid qualifiers="49154">512</eventid>
<version>0</version>
<level>2</level>
<task>0</task>
<opcode>0</opcode>
<keywords>0x80000000000000</keywords>
<timecreated systemtime="2008-04-28t14:17:03.000z" />
<eventrecordid>1018</eventrecordid>
<correlation />
<execution processid="0" threadid="0" />
<channel>application</channel>
<computer>*</computer>
<security />
</system>
<eventdata>
<data>
details:
system writer object failed initialize vss.
system error:
catastrophic failure
</data>
</eventdata>
</event>
when check writers, got this:
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
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: 'frs writer'
writer id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
writer instance id: {881a8c43-69f5-4e21-888f-ec02783c0a0b}
state: [1] stable
last error: no error
writer name: 'asr writer'
writer id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
writer instance id: {eb2ac6bd-f1bb-41b5-8803-19acd27de172}
state: [1] stable
last error: no error
writer name: 'registry writer'
writer id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
writer instance id: {4f778039-8ebe-4752-81d5-d1c4d8c2e5d6}
state: [1] stable
last error: no error
writer name: 'shadow copy optimization writer'
writer id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
writer instance id: {c3c6759f-f973-4e7e-9c90-6aaf1bbede78}
state: [1] stable
last error: no error
writer name: 'bits writer'
writer id: {4969d978-be47-48b0-b100-f328f07ac1e0}
writer instance id: {ed3d9da0-169b-4d3d-8aea-796a680b8d35}
state: [1] stable
last error: no error
writer name: 'com+ regdb writer'
writer id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
writer instance id: {7d413877-2b48-4231-8139-397fbf4492b4}
state: [1] stable
last error: no error
writer name: 'wmi writer'
writer id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
writer instance id: {78b7cbcc-aa19-4cb9-a6ab-fe7e2a061c20}
state: [1] stable
last error: no error
writer name: 'ntds'
writer id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
writer instance id: {000231e2-0b73-4e57-a7e8-68684271a6bf}
state: [1] stable
last error: no error
Windows Server > Windows Server General Forum
Comments
Post a Comment