On Mon, 6 Oct 2008, Kjetil Torgrim Homme wrote:
> > If you allow mixed priority jobs to run simultaneously, you also
> > need some way of flagging a job as "exclusive"
>
> this is accomplished by not setting Allow Mixed Priority on
> BackupCatalog.
OK, it wasn't clear in your earlier description
Alan Brown <[EMAIL PROTECTED]> writes:
> On Mon, 6 Oct 2008, Kjetil Torgrim Homme wrote:
>
>>This directive is only implemented in version 2.5 and later. When
>>set to {\bf yes} (default {\bf no}), this job may run even if lower
>>priority jobs are already running. This means a high
On Mon, 6 Oct 2008, Kjetil Torgrim Homme wrote:
>This directive is only implemented in version 2.5 and later. When
>set to {\bf yes} (default {\bf no}), this job may run even if lower
>priority jobs are already running. This means a high priority job
>will not have to wait for ot
Jason Dixon <[EMAIL PROTECTED]> writes:
> That was just an overview. Each Job is tied to a single client. I
> haven't been able to get this working properly yet; the lower
> priority jobs always "multiplex" (to use a NetBackup term)
> concurrently and force the higher priority job to wait.
My pa
