ADSM-L

Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code

2011-04-26 08:22:10
Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code
From: "Loon, EJ van - SPLXO" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 26 Apr 2011 13:36:21 +0200
Hi TSM-ers!
Thanks for sending me you PMR numbers. I just opened one too and I
referred to your PMR's. Here is mine: 11000,211,788.
Luckily I'm using TSMManager over here, so I have two years of history
to prove that this problem is not a load or scalability issue. I have
one TSM server which hasn't grown during this two year period, because
the libraries are 95% full and no clients are added since.
Again, I urge everybody else who's seeing multiple database backup
triggering during the client backup window to open a PMR too, maybe
together we can convince IBM that there's something broken here.
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
Oscar Kolsteren
Sent: donderdag 21 april 2011 09:23
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi all,

 

I've seen exactly the same after upgrading to 5.5.5.2. I tried to
reschedule client and storage pool backups but still need to make at
least 2 incremental backups a night.

 

Raised PMR with IBM - 65823 999 866
<https://www-946.ibm.com/support/servicerequest/problemDescriptionSelect
.action?userType=0&srNumber=65823&sourceAppl=XSR&retainCountryCode=866&b
ranch=999&sourceNode=prNode5&sourceTranId=558271303370048077&draft=0> .

 

Hope this helps...

 

Best Regards,

 

Oscar Kolsteren

 

 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: 20 April 2011 17:38
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

 

I went back in old emails and found mine from June 2010

 

PMR 93470,487,000

Zoltan Forray

TSM Software & Hardware Administrator

Virginia Commonwealth University

UCC/Office of Technology Services

zforray AT vcu DOT edu <mailto: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
<http://infosecurity.vcu.edu/phishing.html> 

 

 

 

From:

"Loon, EJ van - SPLXO" <Eric-van.Loon AT KLM DOT COM>

To:

ADSM-L AT VM.MARIST DOT EDU

Date:

04/20/2011 11:39 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 Nancy!

Thanks for you PMR number, I will open one too tomorrow.

That's what support told Zoltan too, it's bull!!! We never had any
backup triggering when we were running 5.3, the problems started after
upgrading to 5.5, on all 3 servers. One of them cannot have a higher
load since we do not add additional clients on this server for more than
two years. The library is nearly full on this server.

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
Nancy L Leugemors

Sent: woensdag 20 april 2011 16:20

To: ADSM-L AT VM.MARIST DOT EDU

Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

 

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.Loon AT KLM DOT COM>

To:

ADSM-L AT VM.MARIST DOT 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 AT VM.MARIST DOT 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 AT VM.MARIST DOT EDU] On Behalf Of
Nancy L Leugemors

Sent: maandag 18 april 2011 16:34

To: ADSM-L AT VM.MARIST DOT 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 <moeller AT GWDG DOT DE>

To:

ADSM-L AT VM.MARIST DOT 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 AT VM.MARIST DOT 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 <moeller AT gwdg DOT de
<mailto:moeller AT gwdg DOT 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 <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 <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

********************************************************

 

************************************************************************
********************************************

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager.

 

This footnote also confirms that this email message has been swept by an
antivirus scanner for the presence of computer viruses.

 

ING Direct NV is a limited liability company incorporated in The
Netherlands. Registered in England & Wales, Branch Ref BR7357, 410
Thames Valley Park Drive, Reading, Berkshire, RG6 1RH.

************************************************************************
********************************************

 

------------------------------------------------------------------------
---------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you receive
this message by mistake, you are hereby notified that any disclosure,
reproduction, distribution or use of this message is strictly
prohibited. Please inform the sender by
reply transmission and delete the message without copying or opening it.

Messages and attachments are scanned for all viruses known. If this
message contains password-protected or encrypted attachments, the files
have NOT been scanned for viruses by the ING mail domain. Always scan
attachments before opening them.

ING Direct NV is limited liability company incorporated in The
Netherlands. Registered in England & Wales, Branch Ref BR7357, 410
Thames Valley Park Drive, Reading, Berkshire, RG6 1RH.
------------------------------------------------------------------------
---------------------------------------
********************************************************
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
********************************************************