James,

that was a quick response! thank you so much for looking into this

On Sat, May 21, 2011 at 11:15 AM, James Harper
<james.harper AT bendigoit.com DOT au> wrote:

> You can add a setting to disallow duplicate jobs (see the manual) on a
> per job basis, although when the duplicate tries to run Bacula logs an
> error which can be a bit annoying. It works fine apart from that though.

this is exactly what i have been looking for, cool!

i have set

  Allow Duplicate Jobs = no
  Cancel Queued Duplicates = yes

and indeed subsequent jobs  are being canceled automatically now:

21-May 11:37 bacula-dir JobId 20: No prior Full backup Job record found.
21-May 11:37 bacula-dir JobId 20: No prior or suitable Full backup
found in catalog. Doing FULL backup.
21-May 11:37 bacula-dir JobId 20: Fatal error: JobId 11 already
running. Duplicate job not allowed.
21-May 11:37 bacula-dir JobId 21: No prior Full backup Job record found.
21-May 11:37 bacula-dir JobId 21: No prior or suitable Full backup
found in catalog. Doing FULL backup.
21-May 11:37 bacula-dir JobId 21: Fatal error: JobId 12 already
running. Duplicate job not allowed.
21-May 11:37 bacula-dir JobId 22: No prior Full backup Job record found.
21-May 11:37 bacula-dir JobId 22: No prior or suitable Full backup
found in catalog. Doing FULL backup.
21-May 11:37 bacula-dir JobId 22: Fatal error: JobId 13 already
running. Duplicate job not allowed.

Running Jobs:
Console connected at 21-May-11 11:39
 JobId Level   Name                       Status
======================================================================
    11 Full    BackupSGI.2011-05-21_11.34.27_05 is running
    12 Full    BackupVR.2011-05-21_11.34.27_06 has been canceled
    13 Full    BackupMail.2011-05-21_11.34.27_07 has been canceled
    14 Full    BackupSGI.2011-05-21_11.35.00_08 has a fatal error
    15 Full    BackupVR.2011-05-21_11.35.00_09 is waiting execution
    16 Full    BackupMail.2011-05-21_11.35.00_10 is waiting execution
    17 Full    BackupSGI.2011-05-21_11.36.00_11 has a fatal error
    18 Full    BackupVR.2011-05-21_11.36.00_12 has a fatal error
    19 Full    BackupMail.2011-05-21_11.36.00_13 has a fatal error
    20 Full    BackupSGI.2011-05-21_11.37.00_14 has a fatal error
    21 Full    BackupVR.2011-05-21_11.37.00_15 has a fatal error
    22 Full    BackupMail.2011-05-21_11.37.00_16 has a fatal error

the error message are a bit annoying, that is true (and why are some
jobs marked as canceled while others are marked as fatal errors?) -
but still, this could mean that my dream of having the backup system
doing the right thing when running unattended is coming true :)


thanks again and best regards,

   guenter

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users