ADSM-L

Re: TSM Operational Reporting just stops functioning

2005-09-14 16:57:10
Subject: Re: TSM Operational Reporting just stops functioning
From: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 14 Sep 2005 16:54:49 -0400
Not sure if this relates, but I had a similar problem at one point, and
it ended up being a conflict between the TOR and the actual BA client on
the TOR machine.  The BA client had issues with prompted mode, so the
backup wouldn't start until TOR tried to run it's reports - something
about TOR "woke up" the BA client which then proceeded to monopolize the
connection to the TSM server.  Once we fixed the backup problems, the
TOR issue disappeared.
-steve

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Todd Lundstedt
Sent: Wednesday, September 14, 2005 1:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM Operational Reporting just stops functioning

TOR is 5.3.1.0, running on W2K3.  The hardware also runs ISC/AC, but we
don't use that much.

TOR is set to monitor two TSM servers, one at 5.3, and one at 5.2, both
running AIX, if it matters.

For each TSM server, I have the standard hourly report, and two daily
reports; the standard daily report split up into two - a summary report
and a detail report.

By looking at the current reports in MMC, it appears that TOR simply
stopped running the reports.  The tsmrept service is still running.
There is nothing in the application or system event logs to indicate an
issue.
Looking at the date/time on the last reports run, all of the daily
reports appeared to run at the prescribed time for that day.  The hourly
reports ended up running for their last time at different times (TSM
server1's last hourly report was several hours later than TSM server2's
last hourly report).  Once the hourly reports stop running, subsequent
daily reports will not run, either.

Stopping and starting the tsmrept service "fixes" this for a while.
Sometimes it will work fine for only a day, sometimes for three days.  I
have verified that the "select" commands are not getting to the TSM
server: again, the service is still running.

I deactived the "detail" level report, but that hasn't helped anything.
I found a file "tecinfo.txt" in the Console\TEC folder of TSM.  The log
information there supports my observations; hourly reports running fine,
daily reports running fine, then hourlys stopping for one server, and
then stopping for the other server, and no additional reports after
that, until I stop and start the service.

Any thoughts?

Todd
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm