I said:

> Now, if we could just limit the number of sessions by storage node.

Siobhán Ellis said:

> You can, by defining max sessions per device - laborious, but will work"

And I had to think about that a while.  At first I agreed, but now I've changed 
my mind.  This doesn't completely solve the problem if you're using DDS 
(dynamic drive sharing).  It's very common for a storage node to be connected 
to more tape drives than you want it to use simultaneously.  Suppose you have a 
pool of 20 tape drives that you are sharing among three storage nodes and three 
SAN storage nodes (that back up only their own data).  You may want to allow 
the SAN storage nodes to have access to as many as all 20 of the drives, but 
you probably don't want the regular LAN-based storage nodes to use more than 
two or three at a time.  

You can set max sessions per device, but nothing tells the storage node (or SAN 
storage node) how many devices or sessions it can run simultaneously.  It just 
gets whatever's left over from the server parallelism setting.

+----------------------------------------------------------------------
|This was sent by cpreston AT glasshouse DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER