What triggers a Full?

I have a system which I'm backing up and have it set up for "Always
Incremental" backups.  I ran a Full job by hand and have schedules for
Differentials and Incrementals, and once a week Bacula will roll up and
Incr and Diff jobs greater than 30 days along with the existing Full into a
rolling Full backup.  That all seems to be working fine. What happens,
occasionally, is Bacula will promote an Incremental backup to a Full
Backup. Not to a VirtualFull, an actual Full.  I would assume that
something which might cause an Incr to be promoted to Full would be a
change in the FileSet.  Like I had /data in my includes and /data/temp in
my excludes, and I modified the file to add /data/scratch to the excludes.
Is this assumption correct?

What I'm not sure about, however, are any other changes which might trigger
elevation.
- Permissions change on the fileset.conf file?
- Datestamp on the fileset.conf file?
- other changes to the file unrelated to the fileset, like maybe adding a
comment line, or removing a comment line?

Any thoughts on this, or does someone absolutely have a known list of
things which will promote an Incr to Full, or Diff to Full???

Thanks,
-John

-- 
- Adaptability -- Analytical --- Ideation ---- Input ----- Belief -
-------------------------------------------------------------------
         John M. Lockard |  U of Michigan - School of Information
          Unix Sys Admin |      Suite 205 | 309 Maynard Street
      [email protected] |        Ann Arbor, MI  48104-2211
 www.umich.edu/~jlockard <http://www.umich.edu/%7Ejlockard> |
734-615-8776 | 734-763-9677 FAX
-------------------------------------------------------------------
- The University of Michigan will never ask you for your password -

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users