UNSOLVED
BackUp Errors - VSS
I have 4 servers that with in the past 2 weeks have started giving errors. All VSS Writers are in a stable state without errors.
I have re registered the system writer VSS and all others listed. Done a reboot and restarted services and checked permissions etc.
vssadmin 1.1 - Volume Shadow Copy Service administrative
command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id:
{e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id:
{c27631cd-ad65-4356-96f4-f8dbc7e23232}
State: [1] Stable
Last error: No
error
Writer name: 'FSRM Writer'
Writer Id:
{12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id:
{f787bfb8-6413-4ebe-983b-d5adc14e2db5}
State: [1] Stable
Last error: No
error
Writer name: 'SqlServerWriter'
Writer Id:
{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id:
{aea0b608-0c97-4bce-9493-38d452f1ab2a}
State: [1] Stable
Last error: No
error
Writer name: 'FRS Writer'
Writer Id:
{d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id:
{673b4e35-621e-4fd6-b76c-334f86b01a1c}
State: [1] Stable
Last error: No
error
Writer name: 'ASR Writer'
Writer Id:
{be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id:
{cbbf858f-517e-4cb4-b08a-bbd2901f2666}
State: [1] Stable
Last error: No
error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id:
{4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id:
{79e22a59-f7ad-42e1-aff9-35fd9574e915}
State: [1] Stable
Last error: No
error
Writer name: 'IIS Config Writer'
Writer Id:
{2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id:
{f77679c6-2395-4b71-af6a-82dc15c079a3}
State: [1] Stable
Last error: No
error
Writer name: 'Registry Writer'
Writer Id:
{afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id:
f6a6c8ecc-fe6c-4107-8b55-4dcebcba86f5}
State: [1] Stable
Last error: No
error
Writer name: 'COM+ REGDB Writer'
Writer Id:
{542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id:
{6a350efa-c9b6-4e2a-a1e2-3f5733aa0011}
State: [1] Stable
Last error: No
error
Writer name: 'WMI Writer'
Writer Id:
{a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id:
{1dbbdea4-c17f-4f8a-a17f-042d8eb20da0}
State: [1] Stable
Last error: No
error
Writer name: 'BITS Writer'
Writer Id:
{4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id:
{a75c0768-035a-4994-bfbe-f03de3f61fd0}
State: [1] Stable
Last error: No
error
Writer name: 'NTDS'
Writer Id:
{b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id:
{cf8fd620-03a0-40d4-9aed-d5f7c5baa0af}
State: [1] Stable
Last error: No
error
Writer name: 'IIS Metabase Writer'
Writer Id:
{59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id:
{fe00683d-b865-4082-a6e1-de0186d8ba59}
State: [1] Stable
Last error: No
error
-------------------------------------------------------------------------------------
May 17 04:24:41 Start time: Fri May 17 03:03:00
2013
May 17 04:24:41 End time: Fri May 17 04:24:41 2013
May 17 04:24:41 --- Unsuccessful Save Sets ---
May 17 04:24:41 * Server1:VSS SYSTEM BOOT:\ abandoned
May 17 04:24:41 * : Unable
to execute save job on host server1: Timed out
May 17 04:24:41 * Server1:C:\ abandoned
May 17 04:24:41 * : Unable
to execute save job on host server1: Timed out
May 17 04:24:41 server2:VSS SYSTEM FILESET:\: No full backups of
this save set were found in the media database; performing a full backup
May 17 04:24:41 * server2:VSS SYSTEM FILESET:\ VSS SYSTEM FILESET: ERROR:
sow_save: sfcow_BCDparticipate() returned FALSE.
May 17 04:24:41 * server2:VSS SYSTEM FILESET:\ 7162:save: save of VSS SYSTEM
FILESET:\ to acadbk1 failed
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 * server2:VSS SYSTEM BOOT:\ VSS SYSTEM BOOT: ERROR: Failed to
initialize backup, error=0x80042301: VSS Backup or Restore is not in the
correct state for the operation, or the writer is not in the correct state.
May 17 04:24:41 * server2:VSS SYSTEM BOOT:\ VSS SYSTEM BOOT: ERROR: Failed to get
writers list for VSS SYSTEM BOOT:
May 17 04:24:41 * server2:VSS SYSTEM BOOT:\ 7162:save: save of VSS SYSTEM BOOT:\
to acadbk1 failed
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 server3:VSS SYSTEM FILESET:\: No full backups of
this save set were found in the media database; performing a full backup
May 17 04:24:41 * server3:VSS SYSTEM FILESET:\ VSS SYSTEM FILESET: ERROR:
sow_save: sfcow_BCDparticipate() returned FALSE.
May 17 04:24:41 * server3:VSS SYSTEM FILESET:\ 7162:save: save of VSS SYSTEM
FILESET:\ to acadbk1 failed
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 * server3:D:\ ERROR: Failed to initialize backup,
error=0x80042301: VSS Backup or Restore is not in the correct state for the
operation, or the writer is not in the correct state.
May 17 04:24:41 * server3:D:\ 89668:save: Unable to set up VSS file system
directives. Failed to back up D:\.
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 * server3:C:\ ERROR: Failed to initialize backup,
error=0x80042301: VSS Backup or Restore is not in the correct state for the
operation, or the writer is not in the correct state.
May 17 04:24:41 * server3:C:\ 89668:save: Unable to set up VSS file system
directives. Failed to back up C:\.
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 * server4:VSS SYSTEM FILESET:\ VSS SYSTEM FILESET: ERROR:
sow_save: sfcow_BCDparticipate() returned FALSE.
May 17 04:24:41 * server4:VSS SYSTEM FILESET:\ 7162:save: save of VSS SYSTEM
FILESET:\ to acadbk1 failed
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 * server4:VSS OTHER:\ VSS OTHER: ERROR: Failed to initialize
backup, error=0x80042301: VSS Backup or Restore is not in the correct state for
the operation, or the writer is not in the correct state.
May 17 04:24:41 * server4:VSS OTHER:\ VSS OTHER: ERROR: Failed to get writers
list for VSS OTHER:
May 17 04:24:41 * server4:VSS OTHER:\ 7162:save: save of VSS OTHER:\ to acadbk1
failed
May 17 04:24:41 * : Failed
with error(s)
May 17 04:24:41 * server4:C:\ abandoned
May 17 04:24:41 * : Unable
to execute save job on host server4: Timed out
All 4 servers have the same list of VSS Writers in the same
state. Running Networker 7.6
Since vssadmin list writers shows no error, vss writers are probably
not the cause.Try restarting the volume shadow copy service and make sure
there is enough disk space to create shadow copies on the client.Related thread:
bingo.1
1 Rookie
•
2430 Posts
1036
0
Posted May 20th, 2013 13:00
If these backups fail, it is usually the 'VSS System Writer' which causes trouble.
You can find descriptions how to fix/re-register these from MS.
- For W2K8 this always works for me
- For W2K3 this might not work - then a reboot usually dos the job.