I have been struggling with this issue recently myself, Richard
was kind enough to answer my stupid questions several weeks ago too
*8<). I originally looked at the accounting file, but it did not
contain all of the info that my management and customers wanted so I
wrote my own script that pulls from the actlog and from the events table
to get backup stats and schedule info. If anyone wants a copy of the
script, I will let you have it, it's a korn shell script for Solaris
though. If you just want the backup stats, you can use the query I
started out with (which I pilfered from the Operational reporting tool):
select msgno,nodename,sessid,message from actlog where ( msgno=4952 or
msgno=4953 or msgno=4954 or msgno=4955 or msgno=4956 or msgno=4957 or
msgno=4958 or msgno=4959 or msgno=4960 or msgno=4961 or msgno=4964 or
msgno=4967 or msgno=4968 or msgno=4970 ) and (date_time between
'2004-01-06 19:42' and '2004-01-07 19:42') order by sessid
It dumps out data that looks like:
4952,ALL,60358,"ANE4952I Total number of objects inspected: 50,572 "
4954,ALL,60358,"ANE4954I Total number of objects backed up: 50,572 "
4958,ALL,60358,ANE4958I Total number of objects updated: 0
4960,ALL,60358,ANE4960I Total number of objects rebound: 0
4957,ALL,60358,ANE4957I Total number of objects deleted: 0
4970,ALL,60358,ANE4970I Total number of objects expired: 0
4959,ALL,60358,ANE4959I Total number of objects failed: 0
4961,ALL,60358,ANE4961I Total number of bytes transferred: 2.04 GB
4967,ALL,60358,"ANE4967I Aggregate data transfer rate: 4,602.53
KB/sec "
4968,ALL,60358,ANE4968I Objects compressed by: 0%
4964,ALL,60358,ANE4964I Elapsed processing time: 00:07:46
With a little manipulation with sed:
4952,ALL,60358,"50,572 "
4954,ALL,60358,"50,572 "
4958,ALL,60358,0
4960,ALL,60358,0
4957,ALL,60358,0
4970,ALL,60358,0
4959,ALL,60358,0
4961,ALL,60358,2.04 GB
4967,ALL,60358,"4,602.53 KB/sec "
4968,ALL,60358,0%
4964,ALL,60358,00:07:46
My final script returns an output like (field headers listed first for
reference value):
${NODE},${NODEIPADDRESS},${TSM_SERVER_INFO},${SESSIONID},${SCHEDULENAME}
,${STARTTIME},${ELAPSEDPROCTIME},${NUMOFBYTESXFERRED},${NUMOFOBJECTS},${
NUMOFOBJECTSBACKEDUP},${NUMOFOBJECTSFAILED},${SUCCESSFUL}
AD01-IPP,10.81.10.10,TSM3.USSNTC6,10.81.96.22,60633,DAILY_04,01/13/04
00:53:40,00:01:26,348.72MB,37222,885,0,Completed
AD02-IPP,10.81.10.12,TSM3.USSNTC6,10.81.96.22,61706,DAILY_05,01/13/04
11:59:16,00:01:27,289.16MB,29793,438,0,Completed
ALL,,TSM3.USSNTC6,10.81.96.22,60878,,,00:25:22,2.05GB,50573,50573,0,
CMS-DB1-IPP,10.81.215.11,TSM3.USSNTC6,10.81.96.22,61669,DAILY_06,01/13/0
4 11:38:13,00:02:46,827.55MB,101,85,0,Completed
DEVSTUDIO-IPP,10.81.215.4,TSM3.USSNTC6,10.81.96.22,61573,DAILY_05,01/13/
04 10:45:03,00:02:43,550.66MB,1445,824,0,Completed
At the end of the report is missed:
${MISSEDNODES},${NODEIPADDRESS},${TSM_SERVER_INFO},,${ASSIGNEDSCHEDULE},
${ASSIGNEDSTARTTIME},,,,,,${STATUS}
REPORTDB-IPP,10.81.215.14,TSM3.USSNTC6,10.81.96.22,,DAILY_03,01/13/04
08:00:00,,,,,,Missed
PCLOBS1-IPP,,TSM3.USSNTC6,10.81.96.22,,DAILY_03,01/13/04
08:00:00,,,,,,Missed
S216060SC1SW01,,TSM3.USSNTC6,10.81.96.22,,DAILY_05,01/13/04
10:00:00,,,,,,Missed
Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Robert Ouzen
Sent: Wednesday, January 14, 2004 5:19 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Inconsistency between summary and actlog
Ted
By the way I almost always search for subject dealing with the same
question , but sometimes the answers are very old and quite not
absolutely cleared.
So sorry if I ask again .........
Regards Robert
-----Original Message-----
From: Ted Byrne [mailto:ted.byrne AT ADELPHIA DOT NET]
Sent: Wednesday, January 14, 2004 3:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Inconsistency between summary and actlog
Robert,
As Richard suggested, the many postings to ADSM-L regarding the summary
table's contents (or lack thereof) are very informative.
Among other things, the location of the Accounting records is detailed.
Repeatedly. (The format is recorded in the Admin Guide.)
Before posting a question to ADSM-L, search the message archives on
adsm.org to see if the subject that's vexing you has discussed before.
It's an invaluable resource, and it can save you considerable time in
resolving whatever issue you are facing. Richard's ADSM QuickFacts web
page (http://people.bu.edu/rbs/ADSM.QuickFacts) is another invaluable
resource for the TSM administrator, whether novice or experienced.
Ted
At 02:22 PM 1/14/2004 +0200, you wrote:
>Richard
>
>Thanks for the advice ..... Do you know where I can found the
>format/structure of the accounting records (dsmaccnt.log)
>
>Regards Robert
>
>
>-----Original Message-----
>From: Richard Sims [mailto:rbs AT BU DOT EDU]
>Sent: Wednesday, January 14, 2004 2:19 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Inconsistency between summary and actlog
>
>Robert - As you go through your professional life administering TSM,
>keep one
> thing in mind: the Summary table is unreliable. It has
>historically been unreliable. As testament, see the many postings from
>customers who have
>wasted their time trying to get reliable data from it.
>
>As we keep saying: Use the TSM accounting records as your principal
>source of data for usage statistics. That's what they are there for,
>and they reliably
>contain solid, basic data about sessions. Beyond that, use the
Activity
>Log,
>the Events table, and client backup logs.
>
> Richard Sims, BU
|
