On Thu, Jul 1, 2010 at 10:29 AM, John Drescher <dresche...@gmail.com> wrote: > On Thu, Jul 1, 2010 at 9:45 AM, Jon Schewe <jpsch...@mtu.net> wrote: >> On 7/1/10 8:29 AM, John Drescher wrote: >>> On Thu, Jul 1, 2010 at 9:21 AM, Jon Schewe <jpsch...@mtu.net> 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. >>>> >>> Do you have more than 1 drive? Two different bacula volumes can not be >>> loaded in a single drive. And this does apply to disk volumes as well. >>> >>> >> The log running job was going to disk, the daily job was going to tape. >> > > Have you turned on concurrency? This is off by default. Remember when > turning on concurrency you may have to set "Maximum concurrent Jobs" > in 5 or more places. >
If you have concurrency properly setup. Are your jobs at different priorities. If so then they will not run concurrently. John ------------------------------------------------------------------------------ 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
