Ang: tdp for domino LAN free backup poor performance

2011-05-17 Thread Daniel Sparrman
Hi
 
First off, there are several things that affect the performance except for just 
the optfile, software versions and your operating system:
 
* What speed are you having making the backup over the LAN? 
* How fast are the disks on your Domino server, are they able to transfer data 
at the speeds your tape drives are writing?
* How large are the files on your Domino server (average) ?
* What's the version of the IBMtape driver on your Domino host? The version on 
your TSM server (which controls the library) really doesnt affect read/write 
performance since it only controls the robotics.
 
Have you verified that the backup is actually being done across the SAN and not 
the LAN? 700GB in 30 hours is 23MB/s, which more looks like a slower than 
average LAN backup over gigabit ethernet.
 
If your Domino server cant deliver data to the tapes drives with enough speed, 
you'll end up with a shoeshine effect, which will seriously reduce performance. 
Since you're using IBMtape, I'm assuming you're using some sort of LTO drives. 
If you for example have a LTO3 drive, it will write data @ 80MB/s natively. If 
your host only delivers data at 40MB/s, you will have a drive that is spending 
more time rewinding than actually writing the data. 

Some more information about your environment (hardware on both client & server 
incl tape technology, your TDP configuration file) would be helpful in 
determining the error.
 
Best Regards

Daniel Sparrman
Exist i Stockholm AB
Växel: 08-754 98 00
Fax: 08-754 97 30
daniel.sparr...@exist.se
http://www.existgruppen.se
Posthusgatan 1 761 30 NORRTÄLJE



-"ADSM: Dist Stor Manager"  skrev: -


Till: ADSM-L@VM.MARIST.EDU
Från: Sandeep Jain 
Sänt av: "ADSM: Dist Stor Manager" 
Datum: 05/18/2011 06:54
Ärende: tdp for domino LAN free backup poor performance

HI friends

i am experiencing very very poor backup performance while taking backup of 
domino server.
It is having around 700GB of data and LAN FREE backup on 2 tapes completing in 
30 hours.

OS WIN2k3 64_bit Ent Ed.
Lotus. 8.5.2
TDP for mail 5.5.3
Storage agent 5.5
Version of ibmtape device driver on the Domino windows host that controls tape 
drives---6.2.1.5

i have also tried performance tunning parameters but no luck.

DOMTXNGROUPMAX= 64
DOMTXNBYTELIMIT =2097152


dsm.opt


*==*

* *

* IBM Tivoli Storage Manager for Mail *

* Data Protection for Lotus Domino *

* *

* Sample Options File *

* *

*==*

COMMMethod TCPip

TCPPort 1500

TCPServeraddress 10.3.3.34

TCPWindowsize 63

TCPBuffSize 32

TXNBYTELIMIT 2097152

 

NODename domino_PDCHM_tdp

PASSWORDAccess Generate

 

SCHEDMODE Polling

*SCHEDLOGRetention 14

*SCHEDMODE Prompted

*TCPCLIENTADDRESS yy.yy.yy.yy

*TCPCLIENTPORT 1502

enablelanfree yes

*lanfreecommmethod tcpip

*lanfreetcpport 1500

 

COMPRESSIon NO

COMPRESSAlways NO

 

 

* Exclude all databases named "db1.nsf" regardless of where they appear

*EXCLUDE db1.nsf

* Exclude all databases that match "help5_*" in the "help" subdirectory

*EXCLUDE help\help5_*

* Include all databases in the "mail6" directory

*INCLUDE mail6\...\*

* Assign all databases that match "*.nsf" in the "mail" subdirectory

* to the "MAILDB" management class

*INCLUDE mail\*.nsf* MAILDB

* Exclude all databases in the "mail6" subdirectory from compression

*EXCLUDE.COMPRESSION mail6\...\*

* Encrypt all databases in the "mail5" directory

*INCLUDE.ENCRYPT mail5\...\*

* The Default include/exclude list follows:

*

* Note: You can back up the log.nsf database but you can only restore

* it to an alternate name.

*

EXCLUDE log.nsf

EXCLUDE mail.box

* Include all transaction logs

INCLUDE S*.TXN

TCPNODELAY YES


Regards
Sandeep jain

--
I am using the free version of SPAMfighter.
We are a community of 7 million users fighting spam.
SPAMfighter has removed 18254 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

The Professional version does not have this message

Disclaimer: This e-mail is intended for the sole use of the recipient(s) and 
may contain confidential or privileged information. If you are not the intended 
recipient and receive this message in error, any dissemination, use, review, 
distribution, printing or copying of this message is strictly prohibited, and 
you are requested to notify the sender and destroy all copies of the original 
message. Thank you

tdp for domino LAN free backup poor performance

2011-05-17 Thread Sandeep Jain
HI friends

i am experiencing very very poor backup performance while taking backup of 
domino server.
It is having around 700GB of data and LAN FREE backup on 2 tapes completing in 
30 hours.

OS WIN2k3 64_bit Ent Ed.
Lotus. 8.5.2
TDP for mail 5.5.3
Storage agent 5.5
Version of ibmtape device driver on the Domino windows host that controls tape 
drives---6.2.1.5

i have also tried performance tunning parameters but no luck.

DOMTXNGROUPMAX= 64
DOMTXNBYTELIMIT =2097152


dsm.opt


*==*

* *

* IBM Tivoli Storage Manager for Mail *

* Data Protection for Lotus Domino *

* *

* Sample Options File *

* *

*==*

COMMMethod TCPip

TCPPort 1500

TCPServeraddress 10.3.3.34

TCPWindowsize 63

TCPBuffSize 32

TXNBYTELIMIT 2097152

 

NODename domino_PDCHM_tdp

PASSWORDAccess Generate

 

SCHEDMODE Polling

*SCHEDLOGRetention 14

*SCHEDMODE Prompted

*TCPCLIENTADDRESS yy.yy.yy.yy

*TCPCLIENTPORT 1502

enablelanfree yes

*lanfreecommmethod tcpip

*lanfreetcpport 1500

 

COMPRESSIon NO

COMPRESSAlways NO

 

 

* Exclude all databases named "db1.nsf" regardless of where they appear

*EXCLUDE db1.nsf

* Exclude all databases that match "help5_*" in the "help" subdirectory

*EXCLUDE help\help5_*

* Include all databases in the "mail6" directory

*INCLUDE mail6\...\*

* Assign all databases that match "*.nsf" in the "mail" subdirectory

* to the "MAILDB" management class

*INCLUDE mail\*.nsf* MAILDB

* Exclude all databases in the "mail6" subdirectory from compression

*EXCLUDE.COMPRESSION mail6\...\*

* Encrypt all databases in the "mail5" directory

*INCLUDE.ENCRYPT mail5\...\*

* The Default include/exclude list follows:

*

* Note: You can back up the log.nsf database but you can only restore

* it to an alternate name.

*

EXCLUDE log.nsf

EXCLUDE mail.box

* Include all transaction logs

INCLUDE S*.TXN

TCPNODELAY YES


Regards
Sandeep jain

--
I am using the free version of SPAMfighter.
We are a community of 7 million users fighting spam.
SPAMfighter has removed 18254 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

The Professional version does not have this message

Disclaimer: This e-mail is intended for the sole use of the recipient(s) and 
may contain confidential or privileged information. If you are not the intended 
recipient and receive this message in error, any dissemination, use, review, 
distribution, printing or copying of this message is strictly prohibited, and 
you are requested to notify the sender and destroy all copies of the original 
message. Thank you


Re: 3494 library questions

2011-05-17 Thread Richard Sims
On May 17, 2011, at 10:38 AM, Lee, Gary D. wrote:

> Is there a way to mount / dismount volumes in a particular drive in a 3494 
> library from the shell  prompt?
> I need to run tests on a ts1120 drive and the library is in a remote location 
> with no personell.

To mount: mtlib -l /dev/lmcp0 -m -f /dev/rmt? -V VolName

To dismount:  mtlib -l /dev/lmcp0 -d -f /dev/rmt?
where the question mark is the drive number.
The accessor will then return the cartridge to its cell.
Be sure not to interfere with any host application which has the drive 
allocated.


Re: 3494 library questions

2011-05-17 Thread Thomas Denier
-Gary Lee wrote: -

>Is there a way to mount / dismount volumes in a particular drive in a
>3494 library from the shell  prompt?
>I need to run tests on a ts1120 drive and the library is in a remote
>location with no personell.

We used to have to do this as part of the disaster recovery process
for our mainframe Linux TSM server (in more recent times the recovery
configuration has included a TS3500 rather than a 3494). The commands
we used were as follows:

mtlib -l library -m -f drive -V volume
mtlib -l library -d -f drive -n

where 'library' is the library name (the same one you would specify
for the 'device=' parameter when defining a server to library path
in the TSM database), 'drive' is the tape drive special file (for
example, '/dev/IBMtape0'), and 'volume' is the volume serial number.
The '-n' on the dismount command causes the command to end as soon
as it has asked the library to carry out the operation. In the
absence of this option the command would not end until the library
got the volume back into a storage cell.

Re: 3494 library questions

2011-05-17 Thread Zoltan Forray/AC/VCU
Not quite what you asked for (haven't used the shell/web interface) but
IBMtapeutil  (you did not say what platform - mine are Linux) has
functions to "Load Tape" and "Unload Tape" as well as "Reset Drive"
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.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:
"Lee, Gary D." 
To:
ADSM-L@VM.MARIST.EDU
Date:
05/17/2011 10:53 AM
Subject:
[ADSM-L] 3494 library questions
Sent by:
"ADSM: Dist Stor Manager" 



Is there a way to mount / dismount volumes in a particular drive in a 3494
library from the shell  prompt?
I need to run tests on a ts1120 drive and the library is in a remote
location with no personell.

Thanks for any help you can give.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310


Re: TDP for Mail and Exchange 2010

2011-05-17 Thread Del Hoobler
Ben,

That message can sometimes mean you have a bad entry in the
DSM.OPT file or something else that keeps the TSM API
from loading correctly.

The most expedient way for you to get this resolved is
to open a PMR with IBM support. They can gather a
Data Protection for Exchange and TSM API trace
and find out what is going wrong pretty quickly.

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 05/17/2011
10:38:28 AM:

>> From: Ben Bullock 
>> To: ADSM-L@vm.marist.edu
>> Date: 05/17/2011 10:43 AM
>> Subject: TDP for Mail and Exchange 2010
>> Sent by: "ADSM: Dist Stor Manager" 
>>
>> Folks,
>>I have a question about TDP for Mail. I have been doing it on
>> Exchange 2007 with the legacy backups for a long time with no
>> problems. We are migrating to Exchange 2010 and now you have to
>> back it up using VSS. I must say, this is a complicated procedure,
>> as I found other folks having issues while searching the ADSM-L
archives.
>>
>> Here is the documentation from Tivoli on how to set it up, but due
>> to the various options and iterations, it is lacking in specific
examples:
>> http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/
>> com.ibm.itsm.mail.exc.doc/b_dp_mail_exc_guide_win.pdf
>>
>> I was wondering if anybody had a step-by-step procedure for their
>> environment they would like to share.
>>
>> This is the environment I am working in:
>> TSM server: AIX, TSM V6.2.1
>> Exchange client: Windows 2008 R2, SP1. Exchange 2010
>>BA client v6.2.2 (64-bit), TDP for mail v6.1.3
>> Storage: Just a simple SAN. I don't want to link it with DS, SVC,
>> Netapp snapshots, etc. I just want to push a copy to TSM
>>
>> I can get the BA client working no problem, but after setting up
>> the TDP client and altering its dsm.opt and tdpexc.cfg file and
>> running the "grant proxynode" command on the TSM server, I still
>> get this error:
>>
>> ACN5705W An error was encountered with Tivoli Storage Manager API
>> initialization, rc = 400.
>> Examine the dsierror.log for more information or determine if the
>> TSM API is installed properly.
>>
>> I look at the dsierror.log file and it is not even being written
>> to. I have uninstalled and reinstalled the TDP client, but still
nothing.
>>
>> Any help would be appreciated.
>>
>> Ben
>>
>> [attachment "mg_info.txt" deleted by Del Hoobler/Endicott/IBM]


Re: TDP for Mail and Exchange 2010

2011-05-17 Thread Yudi Darmadi
hai Ben,
Maybe you can try to re-install the TSM Client, instead of TDP, to "fix" the 
API. I think it's Because the versions of  the TSM Client and TDP are different.





Yudi Darmadi
http://www.npp-asia.com
Sent from XL BlackBerry®

-Original Message-
From: Ben Bullock 
Sender: "ADSM: Dist Stor Manager" 
Date: Tue, 17 May 2011 08:38:28 
To: 
Reply-To: "ADSM: Dist Stor Manager" 
Subject: [ADSM-L] TDP for Mail and Exchange 2010

Folks,
   I have a question about TDP for Mail. I have been doing it on Exchange 2007 
with the legacy backups for a long time with no problems. We are migrating to 
Exchange 2010 and now you have to back it up using VSS. I must say, this is a 
complicated procedure, as I found other folks having issues while searching the 
ADSM-L archives.
 
Here is the documentation from Tivoli on how to set it up, but due to the 
various options and iterations, it is lacking in specific examples:
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.mail.exc.doc/b_dp_mail_exc_guide_win.pdf

I was wondering if anybody had a step-by-step procedure for their environment 
they would like to share.

This is the environment I am working in:
TSM server: AIX, TSM V6.2.1
Exchange client: Windows 2008 R2, SP1. Exchange 2010
BA client v6.2.2 (64-bit), TDP for mail v6.1.3
Storage: Just a simple SAN. I don't want to link it with DS, SVC, Netapp 
snapshots, etc. I just want to push a copy to TSM

I can get the BA client working no problem, but after setting up the TDP client 
and altering its dsm.opt and tdpexc.cfg file and running the "grant proxynode" 
command on the TSM server, I still get this error:

ACN5705W An error was encountered with Tivoli Storage Manager API 
initialization, rc = 400.
Examine the dsierror.log for more information or determine if the TSM API is 
installed properly.

I look at the dsierror.log file and it is not even being written to. I have 
uninstalled and reinstalled the TDP client, but still nothing.

Any help would be appreciated.

Ben




3494 library questions

2011-05-17 Thread Lee, Gary D.
Is there a way to mount / dismount volumes in a particular drive in a 3494 
library from the shell  prompt?
I need to run tests on a ts1120 drive and the library is in a remote location 
with no personell.

Thanks for any help you can give.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

TDP for Mail and Exchange 2010

2011-05-17 Thread Ben Bullock
Folks,
   I have a question about TDP for Mail. I have been doing it on Exchange 2007 
with the legacy backups for a long time with no problems. We are migrating to 
Exchange 2010 and now you have to back it up using VSS. I must say, this is a 
complicated procedure, as I found other folks having issues while searching the 
ADSM-L archives.
 
Here is the documentation from Tivoli on how to set it up, but due to the 
various options and iterations, it is lacking in specific examples:
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.mail.exc.doc/b_dp_mail_exc_guide_win.pdf

I was wondering if anybody had a step-by-step procedure for their environment 
they would like to share.

This is the environment I am working in:
TSM server: AIX, TSM V6.2.1
Exchange client: Windows 2008 R2, SP1. Exchange 2010
BA client v6.2.2 (64-bit), TDP for mail v6.1.3
Storage: Just a simple SAN. I don't want to link it with DS, SVC, Netapp 
snapshots, etc. I just want to push a copy to TSM

I can get the BA client working no problem, but after setting up the TDP client 
and altering its dsm.opt and tdpexc.cfg file and running the "grant proxynode" 
command on the TSM server, I still get this error:

ACN5705W An error was encountered with Tivoli Storage Manager API 
initialization, rc = 400.
Examine the dsierror.log for more information or determine if the TSM API is 
installed properly.

I look at the dsierror.log file and it is not even being written to. I have 
uninstalled and reinstalled the TDP client, but still nothing.

Any help would be appreciated.

Ben

The BCI Email Firewall made the following annotations
-
*Confidentiality Notice:

This E-Mail is intended only for the use of the individual
or entity to which it is addressed and may contain
information that is privileged, confidential and exempt
from disclosure under applicable law. If you have received
this communication in error, please do not distribute, and
delete the original message.

Thank you for your compliance.

You may contact us at:
Blue Cross of Idaho
3000 E. Pine Ave.
Meridian, Idaho 83642
1.208.345.4550

-



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

2011-05-17 Thread Mueller, Ken
So perhaps the issue folks are seeing isn't directly caused by a
languishing log pin, but that something in the 5.5.5.0 upgrade made a
questionable change to the database causing corruption/inconsistency?
Or some housekeeping operation changed in 5.5.5.0 that is generating
more/larger transactions or activity log entries, causing the log to
fill quicker than before, thus exposing these previously innocuous log
pins?  Just thinking out loud...

Ken Mueller
Chief Technology Officer
Magna Carta Companies

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Cheung, Richard
Sent: Tuesday, May 17, 2011 3:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code


Hi. I had a server like that - log filled up extremely quickly, multiple
log pins etc.  

I ended up actually doing a full DB DUMP, DB RELOAD, as it turned out to
be something corrupted within my database + logs. It has been generally
running fine ever since.  

I do agree, this is something related to workload for sure, but also do
look at the health of your database and logs - this may be pointing to
possible issues within them. 



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Loon, EJ van - SPLXO
Sent: Monday, 16 May 2011 11:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to
5.5.5.0 code

Hi Richard!
> So is 5.5.5.0 also having this issue with the log pinning?
Yes. As soon as the log hist 80% TSM starts delaying transactions. In
this level a bug was fixed which caused the log to fill too soon after
it reached 80%. I'm running 5.5.5.2 and it's still filling to 80%
multiple times a night. 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
Cheung, Richard
Sent: zondag 15 mei 2011 04:02
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi

The worry about this is I had a PMR opened for this issue on my servers,
which are currently at 5.5.4. I was advised it's a known issue, refer to
APAR IC64438, and the recommended fix is to go to 5.5.5.0

So is 5.5.5.0 also having this issue with the log pinning?

I also believed this was happening in early versions of TSM v6.. But the
later builds are okay - can anyone confirm?


Richard Cheung | Server Engineer | Information Systems | Santos Limited
Santos Centre | 60 Flinders Street Adelaide SA 5000 Australia
Ph +61 8 8116 7125 | 7 Fax +61 8 8116 5073 |   richard.che...@santos.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Dave Canan
Sent: Saturday, 14 May 2011 1:22 AM
To: ADSM-L@VM.MARIST.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
 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@VM.MARIST.EDU] On Behalf 
> Of Richard Rhodes
> Sent: donderdag 12 mei 2011 15:04
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
>
> I h

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

2011-05-17 Thread Cheung, Richard
Hi. I had a server like that - log filled up extremely quickly, multiple log 
pins etc.  

I ended up actually doing a full DB DUMP, DB RELOAD, as it turned out to be 
something corrupted within my database + logs. It has been generally running 
fine ever since.  

I do agree, this is something related to workload for sure, but also do look at 
the health of your database and logs - this may be pointing to possible issues 
within them. 



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, 
EJ van - SPLXO
Sent: Monday, 16 May 2011 11:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi Richard!
> So is 5.5.5.0 also having this issue with the log pinning?
Yes. As soon as the log hist 80% TSM starts delaying transactions. In
this level a bug was fixed which caused the log to fill too soon after
it reached 80%. I'm running 5.5.5.2 and it's still filling to 80%
multiple times a night.
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
Cheung, Richard
Sent: zondag 15 mei 2011 04:02
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi

The worry about this is I had a PMR opened for this issue on my servers,
which are currently at 5.5.4. I was advised it's a known issue, refer to
APAR IC64438, and the recommended fix is to go to 5.5.5.0

So is 5.5.5.0 also having this issue with the log pinning?

I also believed this was happening in early versions of TSM v6.. But the
later builds are okay - can anyone confirm?


Richard Cheung | Server Engineer | Information Systems | Santos Limited
Santos Centre | 60 Flinders Street Adelaide SA 5000 Australia
Ph +61 8 8116 7125 | 7 Fax +61 8 8116 5073 |   richard.che...@santos.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Dave Canan
Sent: Saturday, 14 May 2011 1:22 AM
To: ADSM-L@VM.MARIST.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
 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@VM.MARIST.EDU] On Behalf
> Of Richard Rhodes
> Sent: donderdag 12 mei 2011 15:04
> To: ADSM-L@VM.MARIST.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" 
> To: ADSM-L@VM.MARIST.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" 
>
>
>
> 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