On 09/11/17 10:40, Radosław Korzeniewski wrote: > Hello, > > 2017-09-11 14:09 GMT+02:00 Maciolek, Mark <mark.macio...@unh.edu > <mailto:mark.macio...@unh.edu>>: > > Hi, > > Bacula Version: 9.0.3, First full finished yesterday afternoon, the > incremental scheduled for 1am(Job id 17) changed to a Full > > > 06-Sep 01:05 maux-dir JobId 17: No prior Full backup Job record found. > 06-Sep 01:05 maux-dir JobId 17: No prior or suitable Full backup > found in catalog. Doing FULL backup. > > > Your previous Full job (jobid 16) finished at: 10-Sep-17 16:30 but > above messages are from: 06-Sep 01:05. > So, it seems that you had a jobid 17 started when your last Full (jobid > 16) was still running, so messages and Bacula behavior are correct, IMHO.
If you don't want this to happen in future, you might consider setting Allow Duplicate Jobs = No, Cancel Queued Duplicates = yes in each Job or JobDefs definition. This will prevent a new instance of any backup job from being started, even if called for by the schedule, while an existing instance of the same job is still running. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
