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. 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?
-- Jon Schewe | http://mtu.net/~jpschewe If you see an attachment named signature.asc, this is my digital signature. See http://www.gnupg.org for more information. ------------------------------------------------------------------------------ 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
