Backup Central

Hi

In one of my Tsm Client version 6.3.0 running the systemstate backup got this errors messages.

Did the backup with SNAPSHOTPROVIDERFS VSS and SNAPSHOTPROVIDERFS NONE , same result.

The O.S in this machine is Windows 2003 32Bit and tehe TSM server version is 6.2.30

Regards Robert


11/16/2011 10:31:11 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
11/16/2011 10:31:11 ANS5268W The Microsoft Volume Shadow Copy Services writer 'Registry Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/16/2011 10:31:41 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
11/16/2011 10:31:41 ANS5268W The Microsoft Volume Shadow Copy Services writer 'Registry Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/16/2011 10:32:12 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
11/16/2011 10:32:12 ANS5268W The Microsoft Volume Shadow Copy Services writer 'Registry Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/16/2011 10:32:42 ANS0361I DIAG: VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus failed with hr=VSS_E_WRITERERROR_TIMEOUT
11/16/2011 10:32:42 ANS5268W The Microsoft Volume Shadow Copy Services writer 'Registry Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation.
11/16/2011 10:32:42 ANS5273E A Microsoft Volume Shadow Copy Services writer is in an invalid state after taking a snapshot.
11/16/2011 10:32:42 ANS5258E Microsoft volume shadow copy snapshot initialization failed.
11/16/2011 10:32:42 ANS1327W The snapshot operation for 'HAIFADC02\SystemState\NULL\System State\SystemState' failed with error code: 4353.
11/16/2011 10:32:43 ANS1228E Sending of object 'HAIFADC02\SystemState\NULL\System State\SystemState' failed
11/16/2011 10:32:43 ANS5258E Microsoft volume shadow copy snapshot initialization failed.

11/16/2011 10:32:56 ANS1512E Scheduled event ' < at > 422' failed. Return code = 12.

Hello,

This is error common for win2003 server

11/16/2011 10:32:42 ANS1327W The snapshot operation for
'HAIFADC02\SystemState\NULL\
System State\SystemState' failed with error code: 4353.


Check the vssadmin writers status and in that if any writers are in waiting
for completion or are in failed state,have to refire NT backup with below
command,

ntbackup backup systemstate /f "C:\systemstate_backup.bkf"

if it is successfull ,then no problem,waiting for next schedule,so you have
to check the NT backup is successfull or not ?

and check the systemstate_backup.bkf size,it should be 4kb,if it is less
than 4kb,NT backup failed then have to check with your Wintel team


case:2:in vssadmin writers status one of the writer IIS config writers are
in failed or waiting for completion state,then have to restart the
server,otherwise problem will not fix

Strange ..

I check the vssadmin list writers , everything is O.K

I run the ntbackup backup systemstate /f "C:\systemstate_backup.bkf" without any problem create a file of 1,444,771 KB

Did a ntbackup manually to double check works too fine with same result

But still thru TSM an errors message.

Regards Robert

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of gopi muppidi
Sent: Wednesday, November 16, 2011 4:52 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] stystemstate errors on client 6.3.0

Hello,

This is error common for win2003 server

11/16/2011 10:32:42 ANS1327W The snapshot operation for 'HAIFADC02\SystemState\NULL\ System State\SystemState' failed with error code: 4353.


Check the vssadmin writers status and in that if any writers are in waiting for completion or are in failed state,have to refire NT backup with below command,

ntbackup backup systemstate /f "C:\systemstate_backup.bkf"

if it is successfull ,then no problem,waiting for next schedule,so you have to check the NT backup is successfull or not ?

and check the systemstate_backup.bkf size,it should be 4kb,if it is less than 4kb,NT backup failed then have to check with your Wintel team


case:2:in vssadmin writers status one of the writer IIS config writers are in failed or waiting for completion state,then have to restart the server,otherwise problem will not fix

Hi Robert,

Have you installed the two pre-requisite Microsoft hotfixes, 940349 and
934016, that are described in the Microsoft Windows Client Requirements
page on the TSM support site?

Best regards,

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM < at > IBMUS
Internet e-mail: storman < at > us.ibm.com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L < at > vm.marist.edu> wrote on 2011-11-17
02:44:25:

From: Robert Ouzen <rouzen < at > UNIV.HAIFA.AC.IL>
To: ADSM-L < at > vm.marist.edu
Date: 2011-11-17 02:46
Subject: Re: stystemstate errors on client 6.3.0
Sent by: "ADSM: Dist Stor Manager" <ADSM-L < at > vm.marist.edu>

Strange ..

I check the vssadmin list writers , everything is O.K

I run the ntbackup backup systemstate /f "C:\systemstate_backup.bkf"
without any problem create a file of 1,444,771 KB

Did a ntbackup manually to double check works too fine with same result

But still thru TSM an errors message.

Regards Robert

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On
Behalf Of gopi muppidi
Sent: Wednesday, November 16, 2011 4:52 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] stystemstate errors on client 6.3.0

Hello,

This is error common for win2003 server

11/16/2011 10:32:42 ANS1327W The snapshot operation for 'HAIFADC02
\SystemState\NULL\ System State\SystemState' failed with error code:
4353.


Check the vssadmin writers status and in that if any writers are in
waiting for completion or are in failed state,have to refire NT
backup with below command,

ntbackup backup systemstate /f "C:\systemstate_backup.bkf"

if it is successfull ,then no problem,waiting for next schedule,so
you have to check the NT backup is successfull or not ?

and check the systemstate_backup.bkf size,it should be 4kb,if it is
less than 4kb,NT backup failed then have to check with your Wintel team


case:2:in vssadmin writers status one of the writer IIS config
writers are in failed or waiting for completion state,then have to
restart the server,otherwise problem will not fix