John Lockard jlock...@umich.edu writes:
But, priority also postpones any jobs of higher priority.
If a job, of priority 20 is currently running and you start
off several other jobs, with priorities of 10, 20 and 30, then
the only jobs which will run concurrently will be the jobs
of priority
On Sat, Mar 21, 2009 at 05:10:09AM -0700, Kevin Keane wrote:
John Lockard wrote:
The minimum setting I have on Max Concurrent Jobs is on the
Tape Library and that's set to 3. It appears that priority
trumps all, unless the priority is the same or better.
So, if I have one job that has
John Lockard wrote:
The minimum setting I have on Max Concurrent Jobs is on the
Tape Library and that's set to 3. It appears that priority
trumps all, unless the priority is the same or better.
So, if I have one job that has priority of, say, 10, then
any job running on any other tape drive
Hi All,
I have a mix of disk and tape backups. To disk I allow up to
20 jobs run concurrently. On my tape library I have 3 tape
drives, so only allow a max of 3 jobs to run concurrently.
I run Full backups once a month, Differentials once a week
and incrementals most days of the week. I would
I stand somewhat corrected. I was wrong in stating
that priority of a job on a certain media blocked
only jobs on that media. It actually blocks all other
lower priority jobs from running no matter whether the
lower priority job is on the same media or not.
-John
On Fri, Mar 20, 2009 at
I stand somewhat corrected. I was wrong in stating
that priority of a job on a certain media blocked
only jobs on that media. It actually blocks all other
lower priority jobs from running no matter whether the
lower priority job is on the same media or not.
I find this makes priorities not
The minimum setting I have on Max Concurrent Jobs is on the
Tape Library and that's set to 3. It appears that priority
trumps all, unless the priority is the same or better.
So, if I have one job that has priority of, say, 10, then
any job running on any other tape drive or virtual library
will
