We are working several PMRs now for several customers seeing this issue. We are
recommending certain levels of the server code and client code for customers
seeing this issue. On the server side, we are recommending 5.5.5.0 (which you
or at), or if your environment does a lot of customized reporting with selects,
then we recommend 5.5.5.2. For the client side, the question is whether you
have windows 7 or windows 2008 in your environment. If so, our first choice for
client levels for those machines is 6.1.4.2.
I am out this week on vacation, but if Andy is monitoring the thread maybe he
could add some additional input here. In each of these levels we have
identified potential APARs that could create possible log pinning issues. We
are still pursuing other issues as well. If you are seeing log pinning
problems, we encourage you to open a PMR with IBM software support.
Dave Canan
Advanced Technical Support
TSM Performance
Ddcanan AT us.IBM DOT com
Sent from my iPad
On Jun 1, 2011, at 7:01 AM, "Druckenmiller, David" <drucked AT MAIL.AMC DOT
EDU> wrote:
> Did this issue ever get resolved? I've noticed the same thing for my 5.5.0
> server and have been trying to isolate the issue, but to no avail.
>
> Thanks
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Dave Canan
> Sent: Friday, May 13, 2011 11:52 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0
> code
>
> Andy Raibeck and I have been monitoring this thread for the past few weeks
> and have been having numerous discussions about what we need to do to
> address these problems. In addition, we have noted the many PMRs coming into
> the IBM support queue, and many of these PMRs are now on my queue. Andy will
> be assisting me along with other support people as needed.
>
> As part of this analysis we will be doing, we have a new questionnaire
> (titled "Items to Gather for a PMR with Log Pinning Condition for TSM V5")
> that customers will be filling out that ask several questions regarding your
> environment. We understand that this involves extra work to gather this
> information, but there can be many different areas that can cause log
> pinning conditions, so this information is needed. In addition, there will
> be a script provided (named serverperf5a.pl) that will help us gather
> additional data. Both of these will be provided to you by support. When
> these PMRs are now opened, please make sure that level 1 support adds the
> keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find all
> the PMRs being worked for this issue.
>
> Eric, your PMR is now one that I have on my queue (or I will shortly today).
> We will be contacting you to work the PMR.
>
> Dave Canan
> IBM ATS TSM Performance
> ddcananATUSDOTIBMDOTCOM
> 916-723-2410
>
> On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO <Eric-van.Loon AT klm
> DOT com
>> wrote:
>
>> Hi Rick!
>> You are running in normal mode. In this mode the recovery log only
>> contains uncommited transactions. Don't you agree that in this case, the
>> log should NEVER reach 90%? It should not even reach something like 40%!
>> I don't want to have to implement extra monitoring to keep TSM from
>> crashing. It should just work. Like it did when we were running 5.3...
>> Kind regards,
>> Eric van Loon
>> KLM Royal Dutch Airlines
>>
>>
>>
>>
>>
>> ________________________________________
>> Van: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] namens Loon, EJ
>> van
>> -
>> SPLXO [Eric-van.Loon AT KLM DOT COM]
>> Verzonden: donderdag 12 mei 2011 11:11
>> Aan: ADSM-L AT VM.MARIST DOT EDU
>> Onderwerp: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
>>
>> Hi Paul!
>> We are already running 5.5.5.2 and the log is still filling up, even
>> after switching from rollforward to normal mode.
>> Management currently is questioning whether TSM is the right product for
>> the future. Although I'm a big fan of TSM for 15 years, I'm really in
>> doubt too...
>> Kind regards,
>> Eric van Loon
>> KLM Royal Dutch Airlines
>>
>>
>> On Wed, May 11, 2011 at 9:03 AM, Loon, EJ van - SPLXO
>> <Eric-van.Loon AT klm DOT com
>>> wrote:
>>
>>> 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
>>>
>>>
>>> From: "Loon, EJ van - SPLXO" <Eric-van.Loon AT KLM DOT COM>
>>> To: ADSM-L AT VM.MARIST DOT 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 AT VM.MARIST DOT 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
>>> ********************************************************
>>>
>>>
>> ********************************************************
>> 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
>> ********************************************************
>>
>>
>>
>> -----------------------------------------
>> The information contained in this message is intended only for the
>> personal and confidential use of the recipient(s) named above. If
>> the reader of this message is not the intended recipient or an
>> agent responsible for delivering it to the intended recipient, you
>> are hereby notified that you have received this document in error
>> and that any review, dissemination, distribution, or copying of
>> this message is strictly prohibited. If you have received this
>> communication in error, please notify us immediately, and delete
>> 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
>> ********************************************************
>>
>>
>
> -----------------------------------------
> CONFIDENTIALITY NOTICE: This email and any attachments may contain
> confidential information that is protected by law and is for the
> sole use of the individuals or entities to which it is addressed.
> If you are not the intended recipient, please notify the sender by
> replying to this email and destroying all copies of the
> communication and attachments. Further use, disclosure, copying,
> distribution of, or reliance upon the contents of this email and
> attachments is strictly prohibited. To contact Albany Medical
> Center, or for a copy of our privacy practices, please visit us on
> the Internet at www.amc.edu.
|
