How many mount points / streams per client are you allowing for 750
Clients?

Regards, 

Charles  

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
deehre01 AT LOUISVILLE DOT EDU
Sent: Wednesday, March 09, 2011 8:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] 1024 DB2 database connection limit on AIX

Our maxsessions was 650.   It is now 750.

David

>>> John Monahan <John.Monahan AT US.LOGICALIS DOT COM> 3/8/2011 11:39 PM >>>
Thanks for the info.  What is/was your maxsessions server setting?

_______________________________________
John Monahan
Delivery Consultant
Logicalis, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
deehre01 AT LOUISVILLE DOT EDU
Sent: Tuesday, March 08, 2011 4:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 1024 DB2 database connection limit on AIX

I hit this problem the first night of backups after converting to
V6.2.2.0 from v5.5.  I don't know but I'd guess the determining factor
would be number of nodes backing up.  We have between 400 -500 nodes
backing up.  They back up between 3-5 TB a night.  My v6 db is about 140
GB (used).

David Ehresman

>>> John Monahan <John.Monahan AT US.LOGICALIS DOT COM> 3/8/2011 11:11 AM >>>
http://www-01.ibm.com/support/docview.wss?tcss=Newsletter&uid=swg2142855
7


I'm wondering if anyone on the list has run into this issue or if
someone from IBM can clarify or give examples to quantify slightly
better than "servers with large workloads".  How large a DB?  How many
clients?  How much backed up nightly?  At least give something in the
ballpark so TSM admins can make an educated decision if they need to
consider this problem upfront.  Putting in a large server and then
crossing your fingers that you don't reach the limit isn't really a good
customer support strategy.

Thanks



_______________________________________
John Monahan
Delivery Consultant
Logicalis, Inc.

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.