ADSM-L

Re: [ADSM-L] VSS error

2010-09-15 10:33:39
Subject: Re: [ADSM-L] VSS error
From: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 15 Sep 2010 10:30:53 -0400
I would start by applying the MS VSS hotfix rollup, many issues resolved
with VSS in this package. Due to similar issues we experienced it is now
part of our Win2k3 baseline.
http://support.microsoft.com/kb/940349 

Also, it's worth mentioning that events in the windows event log may be
more helpful in determining the exact problem.

~Rick Adamson
Jacksonville, Fl.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Timothy Hughes
Sent: Wednesday, September 15, 2010 10:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] VSS error


  Hello All,

A windows 2003 Tivoli backup client  using   5.5.2.0 is failing with the
following

question >> If we use the  SNAPSHOTPROVIDERFS VSS  option in the
dsm.opt  would that be a option the solve this

or do we need to install a 2003 patch?

Also, someone said that the latest Windows Tivoli backup client  6.2.1.1
eliminates VSS issues has anyone found that to be true?



09/14/2010 02:40:53 ANS1512E Scheduled event 'MIDNIGHT' failed.  Return
code = 12.
09/15/2010 02:03:14 ANS1959W Removing previous incomplete group '\System
State\0\SystemState' Id:0-450200835
09/15/2010 02:03:18 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2010 02:03:18 ANS5268W The Microsoft Volume Shadow Copy Services
writer 'System Writer' current state (VSS_WS_FAILED_AT_PREPARE_BACKUP)
is not valid for the current operation.
09/15/2010 02:03:19 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
09/15/2010 02:03:49 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2010 02:03:49 ANS5268W The Microsoft Volume Shadow Copy Services
writer 'System Writer' current state (VSS_WS_FAILED_AT_PREPARE_BACKUP)
is not valid for the current operation.
09/15/2010 02:03:49 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
09/15/2010 02:04:19 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2010 02:04:19 ANS5268W The Microsoft Volume Shadow Copy Services
writer 'System Writer' current state (VSS_WS_FAILED_AT_PREPARE_BACKUP)
is not valid for the current operation.
09/15/2010 02:04:19 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
09/15/2010 02:04:49 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITERERROR_RETRYABLE
09/15/2010 02:04:49 ANS5268W The Microsoft Volume Shadow Copy Services
writer 'System Writer' current state (VSS_WS_FAILED_AT_PREPARE_BACKUP)
is not valid for the current operation.
09/15/2010 02:04:49 ANS5271E A Microsoft Volume Shadow Copy Services
writer is in an invalid state before snapshot initialization.
09/15/2010 02:04:49 ANS1327W The snapshot operation for
'Soldor\SystemState\NULL\System State\SystemState' failed with error
code: 4353.
09/15/2010 02:04:49 ANS1228E Sending of object
'Soldor\SystemState\NULL\System State\SystemState' failed
09/15/2010 02:04:49 ANS5258E An error occurred initializing a VSS
request. For more information, see the TSM client error log.

09/15/2010 02:04:49 ANS1375E The snapshot operation failed.

09/15/2010 02:04:49 ANS1999E Incremental processing of '\\Soldor\d$'
stopped.

09/15/2010 02:04:49 ANS5258E An error occurred initializing a VSS
request. For more information, see the TSM client error log.

09/15/2010 02:04:49 ANS1512E Scheduled event 'MIDNIGHT' failed.  Return
code = 12.


C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {62f5e318-fc0e-4ed3-b295-942dbb5ff8c2}
    State: [7] Failed
    Last error: Retryable error

Writer name: 'MSDEWriter'
    Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
    Writer Instance Id: {64dabe0d-1a48-4ef1-aff9-814b83b1a9f2}
    State: [1] Stable
    Last error: No error

Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {8210000a-191a-46e3-acb8-09884ce2998b}
    State: [1] Stable
    Last error: No error

Writer name: 'Event Log Writer'
    Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
    Writer Instance Id: {bccee1c0-6770-4368-b0b6-cef613695fb8}
    State: [1] Stable
    Last error: No error

Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {11c7b420-ab2e-4616-ad09-05ab83802edf}
    State: [1] Stable
    Last error: No error

Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {f6e85119-7db0-4698-84a3-3b2ff0e122f0}
    State: [7] Failed
    Last error: Retryable error

Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {79d24f8e-095f-4e86-97cd-a264ff7a4988}
    State: [1] Stable
    Last error: No error


Thanks for any response in advance!

<Prev in Thread] Current Thread [Next in Thread>