Thanks to everyone who replied with the not so wonderful news on the
performance/recovery log issues.   I have an open case with IBM TSM
Support now and working on it with support now on it.   I will let you
know if I hear anything different once they review my output I sent them
over the weekend.



Nancy Leugemors
Enterprise Systems
HealthNow, NY
716-887-7979



From:
Wolfgang J Moeller <moeller AT GWDG DOT DE>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
04/18/2011 09:46 AM
Subject:
Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



On Apr 17, 2011, Nick Laflamme wrote:
>[...]
> And 5.5.5.2 was just released; this has, among other things, a fix for a
> bug that hangs TSM when you use automatic relabeling of scratch volumes
> (ie, VTL users, usually) and MOVE DRM. I've had 5.5.5.2 on about eight
> servers that had been running 5.5.2.1 or 5.5.3.0, with no observed ill
> effects from the new code after more than a week.

Same here - running 5.5.5.2 since beginning of March (just for LTO-5
support).

Log "max. util" shows values slightly higher than 80% on 3 of 8 relevant
servers,
without any problems that we had noticed (with Logmode = Normal) - that's
about
the same as under previous versions (that's 5.5.3.0 and 5.5.2.1).

So far (and that's since V3.7), the habit of installing server versions
from the "patches" hierarchy when possible, didn't hurt us here ;-).

Best regards,

                 Wolfgang J. Moeller <moeller AT gwdg DOT de>

Tel. +49 551 201-1516 ... not representing ... GWDG, Goettingen, Germany





CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole 
use of the intended recipient(s) and may contain proprietary, confidential, 
trade secret or privileged information.  Any unauthorized review, use, 
disclosure or distribution is prohibited and may be a violation of law.  If you 
are not the intended recipient or a person responsible for delivering this 
message to an intended recipient, please contact the sender by reply email and 
destroy all copies of the original
message.