You do not indicate which version of the TSM client you are running. This
is important, as the elapsed processing time is being reported to the
servr by the client.
There was a problem back in version 4.1.2 where elapsed processing time
was not being reported correctly (it was too short, as you are seeing).
The APAR number is IC29212. Maybe this is the problem. You can find more
info on this by going to http://www.ibm.com and entering the APAR number
as a search argument (top of the page).
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.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Dameon White <dameon_white AT CHARTER DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/28/2003 08:59
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:
My TSM server is 4.2.3.0 on AIX 4.3.3
I am seeing inaccurate values for elapsed processing time
for multiple os platforms, multiple os levels, and
multiple tsm client levels.
I have included one example. Has anyone else seen similar
inaccuracies?
If looking to see how long my backup took, I assume I
should start disregarding the elapsed processing time that
TSM is reporting. Does anyone know of a more accurate
place one should find such data?
02/27/03 21:00:02 ANR2561I Schedule prompter contacting
filesvr01
(session 36725) to start a
scheduled operation.
02/27/03 21:00:03 ANR0406I Session 36726 started for
node filesvr01
(HPUX) (Tcp/Ip 10.172.69.2(54195)).
02/27/03 21:00:04 ANR0406I Session 36728 started for
node filesvr01
(HPUX) (Tcp/Ip 10.172.69.2(54196)).
02/27/03 21:25:56 ANR0403I Session 36728 ended for node
filesvr01
(HPUX).
02/27/03 21:25:58 ANE4952I (Session: 36726, Node:
filesvr01) Total
number of objects inspected:
62,102
02/27/03 21:25:58 ANE4954I (Session: 36726, Node:
filesvr01) Total
number of objects backed up:
218
02/27/03 21:25:58 ANE4958I (Session: 36726, Node:
filesvr01) Total
number of objects updated:
0
02/27/03 21:25:58 ANE4960I (Session: 36726, Node:
filesvr01) Total
number of objects rebound:
0
02/27/03 21:25:58 ANE4957I (Session: 36726, Node:
filesvr01) Total
number of objects deleted:
0
02/27/03 21:25:58 ANE4970I (Session: 36726, Node:
filesvr01) Total
number of objects expired:
1
02/27/03 21:25:58 ANE4959I (Session: 36726, Node:
filesvr01) Total
number of objects failed:
0
02/27/03 21:25:58 ANE4961I (Session: 36726, Node:
filesvr01) Total
number of bytes transferred:
109.31 MB
02/27/03 21:25:58 ANE4963I (Session: 36726, Node:
filesvr01) Data
transfer time:
1,454.74 sec
02/27/03 21:25:58 ANE4966I (Session: 36726, Node:
filesvr01) Network
data transfer rate: 76.95
KB/sec
02/27/03 21:25:58 ANE4967I (Session: 36726, Node:
filesvr01) Aggregate
data transfer rate: 72.02
KB/sec
02/27/03 21:25:58 ANE4968I (Session: 36726, Node:
filesvr01) Objects
compressed by:
0%
02/27/03 21:25:58 ANE4964I (Session: 36726, Node:
filesvr01) Elapsed
processing time:
00:00:54
02/27/03 21:25:58 ANR2507I Schedule FILESVR_BU for
domain DALLAS started at
02/27/03 21:00:00 for node
filesvr01 completed
successfully at 02/27/03 21:25:58.
02/27/03 21:25:58 ANR0403I Session 36726 ended for node
filesvr01
(HPUX).
Thanks for your patience as I rant.
Dameon
|