Oh my god!!!!!!!!! I really thought I was the only one fighting the logpinning issue! My database is filled up to 80% or more at least 20 times a day and all the triggered incrementals have made me running out of scratches multiple times. This very weekend our standby was called again because the recovery log was full on one of our servers. A del volh todate=today-1 type=dbb gave me back 80 tapes, while we only keep 3 days of db backup! About half a year ago I spoke with Zoltan on this very same issue, he already had a case open with IBM and they kept on telling him this was a load related issue. This was keeping me from opening a case too, but after reading this thread, the first thing I'm going to do is upgrade the servers from 5.5.4.0 to 5.5.5.2. If the logpinning is still there (and I think it will be) I will open a case too. I urge everybody else to do the same, because there really is something broken here. Please post your case numer to the list, so we can all refer to each others case. Paul mentioned APAR IC65781, but this APAR mentions an issue when the recovery log hits the 80% full condition. Before we upgraded our 5.3 servers to 5.5.4.0, we never even hit the 80%, not even once a day! That's why I think 5.5.5 will probably keep me from filling up completely, but it will not solve the excessive log usage and incremental backup triggering. Kind regards, Eric van Loon
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nancy L Leugemors Sent: 18 April 2011 16:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code 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 <moel...@gwdg.de> To: ADSM-L@VM.MARIST.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@VM.MARIST.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 <moel...@gwdg.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. ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************
