> > As far as I know (I may be wrong on this one), simultaneous jobs will > only run when they have the SAME priority. In addition to that, the > priority is only taken into account when multiple jobs start at the same > time or get queued, once started, priority is ignored (ie a low priority > job can stop a high priority one from running). > > Greetings, > Michel
Yeah, you are right about the priority. As far as I remember from the manuals the priority is checked before starting the job. Once the job is started bacula waits for it to finish before checking again. However, the execution of simultaneous jobs should be a different business. Why should bacula wait for a job to end on one drive if it has another job to do on a different drive with different tape/volumes. Shouldn't it make the checks to find out if it can do two jobs at a time for 2 drive systems? This would be the logical check to perform of libraries with multiple tapes. It might be the shortcomings of the current bacula version (1.36.3). Or perhaps I've missed something out from the configuration and need to change this. Oh, well, will wait for the thoughts of more users about it. I am sure I am not the only person who might have similar requirements, as libraries with multiple drives are very common. Many thanks for all the help, -- Andrei
signature.asc
Description: This is a digitally signed message part
