Eric, My PMR is 32989,180. I too was told that my TSM server is very busy and maybe it's time to split it off into another instance of TSM. My log pinned again yesterday on a Windows server this time where the other times it was a database backups for different servers.
Please send out your PMRs to the group so we can reference them in our tickets. Thanks everyone who replied, I will let you know the end result if there is any :-) Thank You, Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 From: "Loon, EJ van - SPLXO" <eric-van.l...@klm.com> To: ADSM-L@VM.MARIST.EDU Date: 04/20/2011 04:50 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> Hi TSM-ers! I too upgraded my servers to 5.5.5.2 and the log is still filling up to fast. During last nights backup window, three incrementals were triggered by the db backup trigger. My log is set to 12Gb with the trigger at 75%. I will open a PMR too for this and again, I urge everybody else too do this too. I'm 100% convinced this excessive log utilization is a bug introduced in the 5.5 code. I have never seen any db backup triggering when we were using the 5.3 code. Nancy, could you please post your PMR number to the list, so I can refer to it in my PMR? Thanks!!! Kind regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nancy L Leugemors Sent: maandag 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 ********************************************************
