Thank you, everything worked properly.

2009/9/29 Tchuise, Bertaut <BTchuise AT lmus.leggmason DOT com>

> Bruno,
>
> VSS tends to be fickle at times on Windows system. I have resolved numerous
> VSS issues on W2k3 but none on W2k8 so far; the issues lies within Windows
> not TSM. You could try the following steps:
>
> ** Run the "vssadmin list writers" then check the state of your writers. If
> you have any writers showing failures, restart the COM+ event System
> Notification and COM+ System Application, Volume Shadow Copy and Microsoft
> Software Shadow Copy services.
> ** Check the writers state once more and run a manual system state backup
> with the ntbackup utility. If it runs without issues, then VSS should be
> fine and you system state backup will work within TSM.
>
> We tend to get random VSS issues in our environment; after restarting the
> services above, we don't get those errors back.
> As a last resort, you could re-register you dlls after exporting then
> deleting the subscription hive under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\
>  (restarting the services above will create a new subscription hive in the
> registry) then
>
> cd /d %windir%\system32
> net stop vss
> net stop swprv
> regsvr32 ole32.dll
> regsvr32 oleaut32.dll
> regsvr32 vss_ps.dll
> vssvc /register
> regsvr32 /i swprv.dll
> regsvr32 /i eventcls.dll
> regsvr32 es.dll
> regsvr32 stdprov.dll
> regsvr32 vssui.dll
> regsvr32 msxml.dll
> regsvr32 msxml3.dll
> regsvr32 msxml4.dll
>
> Good luck.
>
> BERTAUT TCHUISE
> TSM/NetApp Storage Administrator
> Legg Mason Technology Services
> *410-580-7032
> BTchuise AT leggmason DOT com
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Bruno Oliveira
> Sent: Tuesday, September 29, 2009 8:44 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] VSS Error
>
> 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
>
> IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason
> therefore recommends that you do not send any confidential or sensitive
> information to us via electronic mail, including social security numbers,
> account numbers, or personal identification numbers. Delivery, and or timely
> delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
> that you do not send time sensitive
> or action-oriented messages to us via electronic mail.
>
> This message is intended for the addressee only and may contain privileged
> or confidential information. Unless you are the intended recipient, you may
> not use, copy or disclose to anyone any information contained in this
> message. If you have received this message in error, please notify the
> author by replying to this message and then kindly delete the message. Thank
> you.
>



-- 
abs,

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