That's the behaviour I've seen when I set Maximum Concurrent Jobs = 1 under JobDefs. Then only one job with the same name can run at a time. What I was hoping for with duplicate job control was for the subsequent job(s) to be canceled so that they wouldn't run at all.
thanks, Stephen Silver Salonen wrote: > Hello. > > I noticed one thing today.. a big full backup was ran on friday, so it wasn't > completed 24 hours later, but when the next job's time arrived, it wasn't > run. > I was very surprised, because I expected it to run as it has been the case > without "allow duplicate jobs = no" with Bacula 2.x. When the full job > completed, the scheduled (and not run) one started immediately and was > correctly making an incremental backup. > > So it seems that duplicate job control does work, just not the way I > expected, > ie. I expected it to being cancelled (I guess I thought it's the "Cancel > Queued Duplicates" directive, but now, I guess not) instead of being hidden > and waiting somewhere back there. > -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu 215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
