No, it's not any of those, I'm afraid:  no pools are shared between tape
and AFTDs, auto media management is not enabled on any devices including
the tape library, and all of the tape drives are still at their default
max sessions (512, same as the AFTDs).

We have our pool selection criteria set by group, and are not
restricting any by device at all.  I guess I could try restricting the
AFTD pools to the AFTD devices.  Come to think of it, that's a good
idea:  if all devices, disk and tape, are valid for a given pool, I
could see Networker waiting for additional volumes to be loaded in the
tape drives rather than allocating the additional sessions to disk.
Since there are no tapes labeled to those pools, and auto media
management is disabled, no tapes match and it sits there and waits.
 
We'll see what restricting the pools does, thanks!


-----Original Message-----
From: Peter Viertel [mailto:Peter.Viertel AT macquarie DOT com] 
Sent: Tuesday, November 20, 2007 4:32 PM
To: EMC NetWorker discussion; Andrew Quintana
Subject: RE: [Networker] Max Sessions ignored, Target Sessions seems to
be hard limit

Have a look at your pool configuration - you should use unique pools for
aftd - eg not shared with tape devices.   Your aftd RW devices should
all be selected in that pool's definition, and auto media management
should not be selected for the aftd devices at all...

Also - in some cases the sessions configs of tape devices on the save
server can interact with your aftd - hard to describe it exactly, but
we've seen it happen, so if you have tape devices, you should try to
make their max sessions higher and see what happens...


> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Andrew Quintana
> Sent: Wednesday, 21 November 2007 4:25 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Max Sessions ignored, Target 
> Sessions seems to be hard limit
> 
> I don't want to pass the additional sessions to another storage node,
> just to the other AFTDs on the same node labeled for the same 
> pool.  We
> have four "Windows" pool volumes, five "Unix", and four "Database"
> volumes.  Example:  if I set Target Sessions on all of them to 2, only
> 10 Unix sessions will run with the rest being queued and calling for
> more volumes in that pool.  I don't want the remaining sessions being
> assigned to another node or another pool, just spread among 
> the volumes
> in that pool.
> 
> -----Original Message-----
> 
> 
> As far as I know, target sessions only work per storage node. Its not 
> until max sessions are reached until a save is refused and passed to 
> another storage node (next in list). But I could be wrong..
> 
> //Oscar

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