We had a similar problem but also with earlier versions.  It seems
that you have to be careful to ensure that all devices for which
the pool is enabled will share the load.  What this means is that
if the pool can use another device, NetWorker wants to allocate
the next session to that device.  (This is even the case if the
device is disabled!)

The easiest way to ensure this is to only allow one pool on an
adv_file device and ensure no other devices are allocated to the pool.


On 21/06/2006, at 4:57 AM, Ballinger, John M wrote:

In the past(v7.2.1) we have used setting target sessions for an adv_file

device to 1 so that savestreams would be distributed across all the

adv_file devices 1 at a time until either all available savestreams were

used up or the server max parallelism was reached. (And both group and
pool maxes are set to 0 so they do not limit.)

But now in v7.3 if we set an adv_file device target sessions to 1 that's all that device gets - period. If we simply set it to 8 then it gets 8. So it's almost like they changed the definition of the 'target sessions'

parameter for a device to now mean Max sessions for that device.

Any one experience the same thing with v7.3 ?

Thanks - John

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 wit 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

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
wit 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