Background operations shouldnt really be the reason for this, since most of
them are actually faster on 6.X than 5.5. Expiration should be faster due to
the ability to control resources for expiration, and copy / move processes
should also be faster due to the performance upgrade of the database.
To find the issue, i'd be looking for clients who isnt behaving naturally.
Check your timings (which clients aren't performing aswell as pre-upgrade)
since that's usually the reason.
My 5 cents worth.
Best Regards
Daniel Sparrman
Exist i Stockholm AB
Växel: 08-754 98 00
Fax: 08-754 97 30
daniel.sparrman AT exist DOT se
http://www.existgruppen.se
Posthusgatan 1 761 30 NORRTÄLJE
-----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> skrev: -----
Till: ADSM-L AT VM.MARIST DOT EDU
Från: "Prather, Wanda" <wPrather AT ICFI DOT COM>
Sänt av: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Datum: 05/15/2011 22:17
Ärende: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Am I correct that scheduling of background processes is important as well?
Don't expiration, migration, backup stgpool also create log transactions?
I'm wondering if it is the housekeeping, rather than the number of client
backups, that is sending my server over the edge.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Friday, May 13, 2011 3:50 PM
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
When I went through this with Andy R, the only solutions we came up with
was:
1. Redistribute the workload/schedules to smooth out the spikes of number of
nodes connecting to perform backups 2. Redistributed / moved nodes to another
TSM server 3. In some cases where we were able to identify nodes causing the
pinning, which was usually Oracle TDP backups, we made changes to break up the
backups into multiple smaller transactions/chunks
This eventually smoothed out the "stair-stepping" of the transaction load
against the logs.
This basically accelerated / gave me an excuse to move nodes to my 6.1.4 server
and any new nodes are create there (or our 6.2.x servers).
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never
use email to request that you reply with your password, social security number
or confidential personal information. For more details visit
http://infosecurity.vcu.edu/phishing.html
From:
Meadows Andrew <Andrew.Meadows AT HCAHEALTHCARE DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
05/13/2011 03:24 PM
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>
We have seen this for quite a while with our TSM servers/Clients. The only
thing we have found that works as a work around is to point our clients to back
up directly to tape. If you are able to find a resolution to this issue please
include me on the resolution as well as I would rather not write backup data
directly to tape during backups.
Thanks,
Andrew
-----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 10: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
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Richard Rhodes
> Sent: donderdag 12 mei 2011 15:04
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
>
> I have a cron job that checks log utilization every 15m. If the log
> goes over 90% the scripts displays a bunch of stuff (q sess, q proc, q
> log, show logpin, etc), runs a show logpin cancel, displays the
> stuff again,
> and finally emails me. (We run in normal mode.) It's been very
> effective
> in preventing a log full condition.
>
> rick
>
>
>
>
>
>
> From: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 05/12/2011 06:11 AM
> Subject: Re: 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,
>
> Dunno if u already looked at these options: THROUGHPUTDATATHRESHOLD
> and THROUGHPUTTIMETHRESHOLD. After a couple of crashes due to log
> filling up, a couple of years back, I standard added them to all my
> clients (with low values to only kill the slowest/hung ones) and
> untill now never had any issues with the V5.5 and below log space
> under normal backup loads.
>
> Log filling only happend when some sys admin made some changes to the
> biggest file servers we had but even this was handled like it should
> be done by ITSM.
>
> Regards,
>
> Karel
>
>
>
> ________________________________________
> 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
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Paul Fielding
> Sent: woensdag 11 mei 2011 20:05
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
>
> Hi folks, if this has already been commented on, my apologies, I
> hvaen't been following closely but just noticed this thread.
>
> We were experiencing log pinned issues after upgrading to 5.5.0.0 code
> at one of my client sites. What we were finding was that,
> occasionally, I'd get up in the morning and look at the server to see
> it completely bogged down with a huge number of backups still
> attempting to run, but nothing was moving - the log was at 84% (over
> it's trigger), and it had been firing off db backups for the last 4h
> to no avail, the log wasn't getting low enough.
>
> A key symptom was that in the actlog we were seeing messages to the
> effect of "Recovery log is at 84%, transactions will be delayed by
> 3ms" (or something like that).
>
> In opening a ticket, it was found there was an issue in the 5.5.0.0
> code where, when the recovery log gets too full, it would start
> delaying transactions in order to prevent the log from filling too quickly.
> However,
> the side effect was that the pinning transaction would also get
> delayed, causing a bit of a never-ending loop. Transactions keep
> getting delayed, pinned transaction never gets to finish, and
> everything would just grind to a halt. I would have to halt the
> server and restart in order to get things back to normal.
>
> IBM recognized this as an issue and recommended going to any 5.5.5.0
> level of code, where the problem was supposed to be fixed. I
> installed 5.5.5.2,
> and the problem has indeed gone away. It was supposed to be fixed at
> 5.5.5.0, though perhaps they didn't quite get it done at that code
> level as they hoped? I'd try installing 5.5.5.2 and see what
> happens....
>
> regards,
>
> Paul
>
>
> 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
> > 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 AT VM.MARIST DOT EDU] On
> > Behalf
> Of
> > Robert Clark
> > Sent: woensdag 11 mei 2011 16:05
> > To: ADSM-L AT VM.MARIST DOT 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.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
> ********************************************************
>
>
|
