Hi Todd, Steve, All,
Ref from Todd:
>> Any idea when 5.3.2 will be out?
I can't be specific but it is targeted for 1st week of October.
>> And are there any known incompatibilities between the 5.3.2 TOR and
>> the 5.2.2.5 AIX servers or 5.3.1.0 AIX servers?
There are no incompatibilities with any version of TOR and any version
of a supported level of server (5.2.2+, 5.3.0+) on any platform. While
technically not supported for earlier server versions TOR will also report
on them as long as the server is running in English.
>> In that respect, because 5.2.6.1 should already have the fix in
>> place, shouldn't I be able to remove my 5.3 TOR install, and go
>> with the 5.2.6.1 TOR?
TOR is part of the management console that ships with the Windows TSM
server and the Windows TSM storage agent. It's also available in a
stand-alone package which you and Bill B. mentioned.
You can only downlevel TOR if you are running the stand-alone package.
You would effectively have to downlevel the server or storage agent to
downlevel TOR in one of the integrated packages because the stand-alone
package can't be installed on a machine running the windows server or
storage agent (because it's already built in to those)
>> And will the 5.2.6.1 TOR work with a 5.3 server?
Yes, no problem. At this point the 5.2 and 5.3 versions have an
identical code base so the only difference is which defects are fixed
by the time the 5.2 or 5.3 version goes out.
>> If so, are there clear instructions around for downleveling TOR?
If TOR 5.2.x.x is installed it can be upgraded by running the TOR
5.3.x.x install.
If TOR 5.3.x.x is installed, just uninstall it, and then run the
5.2.x.x install.
In both cases all of your settings and customizations will be
maintained.
Ref from Steve:
>> I would suspect IC44976, since Todd noted that TOR would work for a
>> day or two before entering the Twilight Zone. I have also been
>> bitten by the expired admin pwd bug, but that stopped TOR cold in
>> my case, so I didn't think it fit this particular problem.
Steve, good point. I mentioned this for completeness and for general
information in case others have the issue of tsm not sending
reports. Password are pretty straight forward and quick to check but
the resource leak symptoms may vary making it a bit harder to confirm.
If there's just one server being reported on then an expired pwd will
stop all reports. If more than one server is being reported on then
reports will continue for the other servers giving the appearance it's
running for several days before stopping. For example, there are 4
worker threads (w1..w4) by default. If 2 servers s1,s2 are getting
daily reports and s1 report runs at 6am and s2 report runs at 7.
d1. s1 report is okay, s2 report not generated (w1 consumed)
d2. s1 report is okay, s2 report not generated (w2 consumed)
d3. s1 report is okay, s2 report not generated (w3 consumed)
d4. s1 report is okay, s2 report not generated (w4 consumed)
d5. TOR is running but no reports are generated because all worker
threads are consumed.
This can take different amounts of time depending on the number of
servers reported on and whether hourly monitors are running, etc.
Similarly, the resource leak takes place each time a report or monitor
runs, so if you are only generating a daily report for a single server
it will run for a long time before the problem appears, but the more
servers, especially if they are all running hourly monitors, the
quicker the problem will appear.
The bottom line. If TOR runs for awhile and stops it's likely to be one
of these apars. If you notice a particular server not being reported on
it's likely the pwd. If a particular server runs for a few days and
stops, it's likely the resource leak.
Thanks for your input. Best Regards, Mike Collins, emcollin AT us.ibm DOT com
|
