Problems with VSS are common/constant.  Did you apply all the recommended 
M$ patches for VSS (no, they don't seem to come in with the regular 
service). 

Here is a M$ page with various VSS problems described and an "update 
rollup package" for VSS:

http://support.microsoft.com/kb/940349

We backup hundreds of 2K3 servers and any time a TSM/VSS problem pops-up, 
it usually goes away with them applying these VSS patches!



From:
Bruno Oliveira <brnolvr84 AT GMAIL DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
09/29/2009 08:44 AM
Subject:
[ADSM-L] VSS Error
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Hi,

I have a TSM v5.5 server running on a Windows 2003 and a TSM v6.1
client running Windows 2008. That has errors during the copy of 
SystemState
only, file copy is normal.

In dsmerror.log appears the following error message:

*09/29/2009 09:22:19 ANS1959W Removing previous incomplete group '\System
State\0\SystemState' Id:0-2609054
09/29/2009 09:22:21 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus() failed with
hr=VSS_E_WRITERERROR_NONRETRYABLE
09/29/2009 09:22:21 ANS5269E The Microsoft Volume Shadow Copy Services
writer 'NTDS' current state (VSS_WS_FAILED_AT_POST_SNAPSHOT) is not valid
for the current operation or cannot be determined.  The last error 
reported
is '800423f4'.
09/29/2009 09:22:21 ANS5271E A Microsoft Volume Shadow Copy Services 
writer
is in an invalid state before snapshot initialization.
09/29/2009 09:22:21 ANS5250E An unexpected error was encountered.
   TSM function name : baHandleSnapshot
   TSM function      : BaStartSnapshot() failed.
   TSM return code   : 4353
   TSM file          : backsnap.cpp (3745)
09/29/2009 09:22:21 ANS1327W The snapshot operation for
'PROBHSRV01\SystemState\NULL\System State\SystemState' failed with error
code: 4353.
09/29/2009 09:22:21 ANS5283E The operation was unsuccessful.
*
Searching the internet for codes spotted the following sites:

*
http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB560&dc=DB520&uid=swg21392932&loc=en_US&cs=UTF-8&lang=en&rss=ct663other

*<
http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB560&dc=DB520&uid=swg21392932&loc=en_US&cs=UTF-8&lang=en&rss=ct663other
>
*
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm.messages.doc/msgs6603.html

*<
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm.messages.doc/msgs6603.html
>
*http://www-01.ibm.com/support/docview.wss?uid=swg21295294*<
http://www-01.ibm.com/support/docview.wss?uid=swg21295294>

None of the solutions proposed by IBM decided. I am having 12 GB available
on C: \ drive, I made a copy of the volume using the Windows and returned
the following output:

*vssadmin 1.1 - Ferramenta de linha de comando administrativa de c¢pias de
sombra de volume
(C) Copyright 2001-2005 Microsoft Corp.*
*Cópia de sombra para 'C:\' criada com êxito
    Identificação da cópia de sombra: 
{82bfd321-5616-49ec-b01e-e77043d0a158}
    Nome do volume da cópia de sombra: **
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy68*<
file:///?\GLOBALROOT\Device\HarddiskVolumeShadowCopy68>

Does anyone know why this error is happening on the copy of SystemState?
-- 
abs,

Bruno Oliveira
Beagá - Minas Gerais - Brazil
55 31 9342 4111