If you don't want to set that GLOBALLY for fear that it may affect some
of your clients that can't handle multiple jobs simultaneously, then you
can set this for individual clients using the bpclient command.

/usr/openv/netbackup/bin/admincmd/

bpclient -add -client $CLIENTNAME -max_jobs <1-99>

There are a lot of other control features that make this CLI *very*
useful

HTH

David A. Chapa * Technical Advisor, Technical Marketing * ADIC *
720.249.5836 * david.chapa AT adic DOT com

Pathlight VX - Integrated Disk-to-Tape Backup - http://www.adic.com


-----Original Message-----
From: Steve Mickeler [mailto:steve AT warning DOT ca] 
Sent: Monday, October 20, 2003 11:19 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] only 1 backup job running at a time


Duh.

Forgot to set Max Jobs per client in Global Attributes.

You tell its been a couple of years since I setup a new master server :)


On Tue, 21 Oct 2003, Steve Mickeler wrote:

>
> Using NBU 4.5 FP5 on Solaris 8 with SSO sharing 4 drives between 6
> servers.
>
> When I initiate a manual backup of any of the policies, it only sets
one
> of the jobs as Active and puts the other jobs into a Queued state
until
> the first job is done.
>
>
> My backup policies have "Allow mutliple data stream" turned on and
"Limit
> jobs per policy" set to 10
>
> Under files Im using anywhere from 2 to 5 NEW_STREAM directives
depending
> on the server.
>
> Any reason why this is happening ?
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu