Ah yes, it really is *yes* by default according to manual, but actually that's
not the case. I've read it multiple times, but I've always misread it :)
--
Silver
On Monday 05 October 2009 13:45:11 Nicolae Mihalache wrote:
> Well, the manual reads like this:
>
>
>
> Allow Higher Duplicate
Well, the manual reads like this:
Allow Higher Duplicates =
If this directive is set to *yes* (default) the job with a higher
priority (lower priority number) will be permitted to run. If the
priorities of the two jobs are the same, the outcome is determined by
other directives (see be
On Friday 31 July 2009 11:41:29 Bram Vandoren wrote:
> Dear All,
> Bacula (3.0.2) is configured to make daily backups of some systems. Full
> backups unfortunately take more then one day to complete and I want to
> avoid that duplicate jobs start (or are queued) before the full backup
> is complete
Dear All,
Bacula (3.0.2) is configured to make daily backups of some systems. Full
backups unfortunately take more then one day to complete and I want to
avoid that duplicate jobs start (or are queued) before the full backup
is completed.
No duplicate job control directives are configured. If I un
Folks,
I am a little confused and hope that you can help me out.
Does the "duplicate job control" feature work in 3.0.0 or not?
It does not work for me and for some others on this mailing list, but
there's been some other threads that don't directly confirm whether this
feature works or not.
Hello,
I was excited to take advantage of the Duplicate Job Control feature in
3.0.0 but it does not appear to be working. At first I assumed the
defaults listed on the New Features documentation page, then later
explicitly defined them in my jobdefs config:
JobDefs {
Name = "DefaultJob"
