ADSM-L

Re: 4.1.2.12 Client Reporting Erroneous Elapsed Processing Time

2001-03-26 10:55:46
Subject: Re: 4.1.2.12 Client Reporting Erroneous Elapsed Processing Time
From: Andy Raibeck <Andrew_Raibeck AT TIVOLI DOT COM>
Date: Mon, 26 Mar 2001 07:56:17 -0800
Hi Anne,

This is a known defect, and is documented in APAR IC29212. I don't have an
ETA for an available fix, though.

So sorry for the "fuzzy math".

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: araibeck AT tivoli DOT com
"The only dumb question is the one that goes unasked."


"Short, Anne" <anne.short AT LMCO DOT COM>@VM.MARIST.EDU> on 03/26/2001 08:35:11
AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  4.1.2.12 Client Reporting Erroneous Elapsed Processing Time



Anybody else notice this?  Since the upgrade to TSM Client to version
4.1.2.12 on our NT 4.0 nodes, the elapsed time for our backups is getting
reported wrong.  The particular node I've documented below starts its
backup
at 8:00 pm (and yes, I've verified it's starting on time).  You'll notice,
that starting on 03/22/2001, the "Elapsed processing time" is getting
reported to be 3 hours or less even though the backup isn't finishing until
well past 2:00 am.  Perhaps its only reporting the elapsed processing time
for the last session that starts, as we let this client run multiple
sessions.

03/22/2001 03:12:19  ANE4964I (Session: 7873, Node: GBNF01)  Elapsed
processing time:  00:03:33
03/23/2001 03:14:04  ANE4964I (Session: 9582, Node: GBNF01)  Elapsed
processing time:  00:00:44
03/24/2001 04:07:38  ANE4964I (Session: 840, Node: GBNF01)  Elapsed
processing time:  00:02:11
03/25/2001 02:20:52  ANE4964I (Session: 1753, Node: GBNF01)  Elapsed
processing time:  00:03:38
03/26/2001 02:26:19  ANE4964I (Session: 3168, Node: GBNF01)  Elapsed
processing time:  00:00:57


Before the upgrade (version 3.7.2), the elapsed processing time was getting
reported correctly:

03/14/2001 03:16:18  ANE4964I (Session: 329, Node: GBNF01)  Elapsed
processing time:  07:15:18
03/16/2001 02:36:29  ANE4964I (Session: 361, Node: GBNF01)  Elapsed
processing time:  06:35:25


Considering we get measured on getting all our backups completed within an
8
hour window, I shouldn't complain as this new math will certainly make us
look good!!  :-)  But, I guess I'll report it as a bug to Tivoli.

Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland
301-240-6184
CODA/I Storage Management
<Prev in Thread] Current Thread [Next in Thread>