Eduardo Júnior <ihtraum18 AT gmail DOT com> writes:

> what's the reasons to a new FULL job to be created?  I mean, after a
> scheduled FULL job, another is started automatically.
>
> I asked this because last night, a new job FULL for a client was
> started without any change in the File Set or a manual execution.

Bacula checks for existing Full jobs at the scheduled time, not when the
job starts.  (at least it used to do this, might be fixed in 5.0.)
anyway -- if your Full job does not finish in 24 hours (yes, this
happens for slow clients with lots of small files :/), the Incremental
may be automatically upgraded to Full.

I use these settings to make sure it doesn't happen:

  Allow Duplicate Jobs = no
  Cancel Lower Level Duplicates = no
  Cancel Queued Duplicates = yes
  Cancel Running Duplicates = no

with this setting, the Incremental in the example will be cancelled, in
my opinion it is better to try again next evening than to run the
Incremental at some random time when the Full is done...

-- 
Kjetil T. Homme
Redpill Linpro AS - Changing the game


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users