ADSM-L

Re: strange incremental behavior on Windows 5.2.2.0

2005-08-10 09:52:16
Subject: Re: strange incremental behavior on Windows 5.2.2.0
From: Steve Schaub <Steve_Schaub AT BCBST DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 10 Aug 2005 09:51:51 -0400
This did fix the problem.
I guess I better get all of our 2003 servers upgraded soon.
Thanks for the assist, Richard & Andy!
-steve

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Raibeck
Sent: Tuesday, August 09, 2005 4:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] strange incremental behavior on Windows 5.2.2.0

I concur. The

08/07/2005 18:10:46 gtUpdateGroupAttr() server error 4 on update
SYSTEMSTATE\SYSFILES

message in the error log is a symptom of that APAR, too.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
Raibeck/Tucson/IBM@IBMUS Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-08-09
12:11:54:

> Maybe this one?
>
>
>
>
>
> IC38377: Backup of Windows2003 System Object fails - ANS1950E - caused
> after a Microsoft VSS_E_PROVIDER_VETO error
>
>
>   A fix is available
> IBM Tivoli Storage Manager V5.2 Fix Pack 3 Clients and READMEs <
> http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg24007407>
>
>
> APAR status
> Closed as program error.
>
>
> Error description
> The backup of the Windows2003 System Object with:
>
> ANS1950E Backup via Microsoft Volume Shadow Copy failed.  See error
> log for more detail.
>
> The error reported in the dsmerror.log is:
>
> CreateSnapshotSet():  pAsync->QueryStatus() returns
> hr=VSS_E_PROVIDER_VETO
>
> It has also been reported that after this failure, subsequent
> incremental backups of the Windows 2003 system object may fail
> with:
>
> ANS1304W Active object not found
> Local fix
> Problem summary
> ****************************************************************
> * USERS AFFECTED: All TSM B/A client v5.2.0 v5.2.2 on          *
> *                 Windows 2003.                                *
> ****************************************************************
> * PROBLEM DESCRIPTION: See ERRROR DESCRIPTION.                 *
> ****************************************************************
> * RECOMMENDATION: Apply fixing PTF when available.             *
> *                 This problem is currently projected          *
> *                 to be fixed in PTF level 5.2.3.              *
> *                 Note that this is subject to change at       *
> *                 the discretion of IBM.                       *
> ****************************************************************
> If BACKUP SYSTEMSTATE or BACKUP SYSTEMSERVICES on Windows 2003 fails,
> subsequent incremental backups of the Windows 2003 system state or
> system service may fail with the message "ANS1304W Active object not
> found".
> Backup processing halts after the ANS1304W message is issued, even if
> there are more files to process.
> Problem conclusion
> The client code has been fixed so that after a system state or system
> services backup failure, subsequent attempts will not fail (barring
> any other conditions that might cause a failure).
> Temporary fix
> Windows interim fix 5.2.2.5
>
> IC38377: Backup of Windows2003 System Object fails - ANS1950E - caused
> after a Microsoft VSS_E_PROVIDER_VETO error
>
>
>   A fix is available
> IBM Tivoli Storage Manager V5.2 Fix Pack 3 Clients and READMEs <
> http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg24007407>
>
>
> APAR status
> Closed as program error.
>
>
> Error description
> The backup of the Windows2003 System Object with:
>
> ANS1950E Backup via Microsoft Volume Shadow Copy failed.  See error
> log for more detail.
>
> The error reported in the dsmerror.log is:
>
> CreateSnapshotSet():  pAsync->QueryStatus() returns
> hr=VSS_E_PROVIDER_VETO
>
> It has also been reported that after this failure, subsequent
> incremental backups of the Windows 2003 system object may fail
> with:
>
> ANS1304W Active object not found
> Local fix
> Problem summary
> ****************************************************************
> * USERS AFFECTED: All TSM B/A client v5.2.0 v5.2.2 on          *
> *                 Windows 2003.                                *
> ****************************************************************
> * PROBLEM DESCRIPTION: See ERRROR DESCRIPTION.                 *
> ****************************************************************
> * RECOMMENDATION: Apply fixing PTF when available.             *
> *                 This problem is currently projected          *
> *                 to be fixed in PTF level 5.2.3.              *
> *                 Note that this is subject to change at       *
> *                 the discretion of IBM.                       *
> ****************************************************************
> If BACKUP SYSTEMSTATE or BACKUP SYSTEMSERVICES on Windows 2003 fails,
> subsequent incremental backups of the Windows 2003 system state or
> system service may fail with the message "ANS1304W Active object not
> found".
> Backup processing halts after the ANS1304W message is issued, even if
> there are more files to process.
> Problem conclusion
> The client code has been fixed so that after a system state or system
> services backup failure, subsequent attempts will not fail (barring
> any other conditions that might cause a failure).
> Temporary fix
> Windows interim fix 5.2.2.5
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm