Hi Stan,

on third thoughts...there is another possibility.

 Check the pool parallelism :

  pool:   properties > configuration > max parallelism

default is 0 (unlimited)
is it 2? 

jee


On Thursday 02 June 2011 17:21:12 jee wrote:
> Hi bingo,
>
>
> That's a good point but that information is on the first msg:
>
> "each drive has 16 as its target sessions value. This is with NetWorker 7.6
> SP1 on a Linux box."
>
> So, I asume  "max sessions" >= 16 (default is 512, I think.)
>
>
> The problem may not be caused by the settings on these two drives. If there
> are other drives on that SN, then the lowest target sessions configured on
> any device on that SN will be used  (even if that other device is linked to
> a different pool). This information appears on the admin guide.
>
> Having the "target sessions" parameter on the device configuration seems to
> be pointless, at first.  However, on second thoughts, it does make sense
> because there isn't a "NSR storage node" type available.  So this attribute
> will have to be configured on the devices (a  dedicated SN is defined that
> way).
>
>
>
> Stan,
>
>  do you have more devices on that SN? If not, then I have run out of
> ideas...or maybe this is a bug?.
>
>
> jee
>
> On Thursday 02 June 2011 07:16:35 bingo wrote:
> > You can limit the device sessions by using the Max. Sessions parameter.
> > As you did not mention it so far, i could think that you might use a NW
> > version which does not have this incorporated yet.
> >
> > On the other hand, if you set the device's Target Sessions high enough,
> > NW should not use another device before the first has been filled to the
> > Target Session value, unless you have 'mis-pooled' and other save sets
> > like Index and Bootstrap must use another media (for another pool).
> >
> > +----------------------------------------------------------------------
> >
> > |This was sent by carsten_reinfeld AT avus-cr DOT de 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
>
> 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

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