On Thursday 01 July 2010 03:21:23 pm Jon Schewe wrote: > So I've got a job that takes over 48 hours to complete (I'm working on > fixing this), but in the meantime I have a second job scheduled to > happen daily writing to a different pool. 2 odd things happened: > 1) The second job couldn't run at the same time as a long job. This > might be because bacula can't spool 2 jobs at once, or I've got to > change something for this.
A device can only handle one volume at a time, even if you write to disk. Maybe the jobs on hold using a different volume have been set to the same device? > 2) So while the long job was running the daily job was paused until the > long job finished (as I explained in 1), the really annoying thing was > that a second daily job was put in the schedule queue even though there > was one already scheduled and waiting, so when the long job finished, > each of my clients was backed up twice again inside of 6 hours, rather > than the second daily job just being dropped (which I would have > expected). Is there a way to change this behavior? > Machiel. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
