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
