Most nodes are defined with the default settings of Maximum Mount Points
Allowed = 1.
Under client Nodes, Advanced Settings the Maximum allowed can be
increased.  (1-999)
On the newer version of the client, one thread is used for communication
and one thread is used to send data.
I currently set maximum =4 on my servers with the oracle applications.
You should try increasing the maximum one at a time.  This allows a
faster through put, but increase it 
to much and you will see a decrease in through put.  Memory and band
width are your concerns. 

Good luck!




Philip A. James
System Software Specialist
UNIX/Linux Services
California Public Employees' Retirement System
Phone: (916) 795-3715
E-Mail: phil_james AT calpers.ca DOT gov
CalPERS


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Denier
Sent: Wednesday, February 06, 2008 12:13 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: max mount point exceeded for a node


-----Richard Rhodes wrote: -----

>We have a server that is using  Oracle/Rman/TDPO/LanFree backups. The 
>node is set to allow 2 mount points.  Yesterday at the start of a 
>backup TSM threw out an error saying that channel 2 could not be 
>allocated because the node had exceeded it's mount points:

When my site started using TDPO we regularly saw similar failures. We
never figured out why TDPO needed so many mount points, but we now
configure TDPO client nodes to allow two mount points per backup stream,
and almost never run out of mount points. As far as I can tell, the rare
cases where we do run out of mount points involve recovery from
interrupted TCP sessions.

I should note that our backups are written to sequential disk volumes. I
would probably be a lot more worried about the extra mount points if we
were sending backups directly to tape.