Hi Robert! Thanks you very much for your reply! Several others on this list reported this behavior and (as far as I know) three other users opened a PMR too. I hope they have more luck, because I'm stuck. Level 2 keeps on saying that the log keeps on growing because of slow running client sessions. Indeed I see slow running client sessions, but they are slowed down by the fact that TSM is delaying all transactions because the log is used for more that 80% during a large part of the backup window! Now they refuse to help me, unless I buy a Passport Advantage contract!!!!!! 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 Robert Clark Sent: woensdag 11 mei 2011 16:05 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code I believe we've been seeing this problem as well. One night in the busiest backup period, I issued a "q actlog begint=now-00:30", and got no results back but an error. I started dsmadmc -console on that server, and could see that the console output was most of an hour behind. (And the console output was scrolling so fast that it could barely be read.) In that case, I think we determined that SQL LiteSpeed was set to some rediculously small transaction size, and this was causing way too many actlog entries. I think I also noted that the session number incremented by something like 100,000 in an hour. Asking the users of SQL LiteSpeed to make some changes was enough to rememdy this problem, although we continue to fight with the logs getting full. Thanks, [RC] From: "Loon, EJ van - SPLXO" <eric-van.l...@klm.com> To: ADSM-L@VM.MARIST.EDU Date: 05/11/2011 02:05 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! Here is a small follow up on my PMR about the recovery log utilization. I'm at TSM level 2, still trying to convince them that there is something broken in the TSM server code. To convince them, I have changed the logmode to normal on one of my servers. I created a graph (through TSMManager) which shows the recovery log utilization during last night's client backup window and is doesn't differ much from the night before, with logmode rollforward. When running in normal mode, TSM should only use the recovery log for uncommitted transactions, so utilization should be very low. My log is 12 Gb and the backuptrigger value (75%) was still hit twice! This clearly shows that there is something wrong with TSM, let's hope I can convince Level 2 too, so my case gets forwarded to the lab. I'll keep you guys posted! Kind regards, Eric van Loon KLM Royal Dutch Airlines ******************************************************** 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 ******************************************************** U.S. BANCORP made the following annotations --------------------------------------------------------------------- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. --------------------------------------------------------------------- ******************************************************** 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 ********************************************************
