from the docs:
Ignore FileSet Changes = <yes|no>
Normally, if you modify the FileSet Include or Exclude lists,
the next backup will be forced to a Full so that Bacula can
guarantee that any additions or deletions are properly saved.
If this directive is set to yes, any changes you make to the
FileSet Include or Exclude lists, will not force a Full during
subsequent backups.
The default is no, in which case, if you change the Include or
Exclude, Bacula will force a Full backup to ensure that
everything is properly backed up. We strongly recommend against
setting this directive to yes, since doing so may cause you to
have an incomplete set of backups.
On Wed, 2007-07-11 at 11:04 -0700, Craig White wrote:
> On Wed, 2007-07-11 at 12:59 -0500, Zeratul wrote:
> > Hi
> >
> > Every time when I'm doing a change in the FileSet for a client, the next
> > backup is upgraded to Full from Incremental. There is any posibility to
> > avoid
> > this behavior? Sometimes the changes are really small but the full backup
> > takes a lot of space and time. Any idea will be appreciated.
> ----
> having recently experienced that same issue, I can answer that one...no
>
> Therefore, I only make changes to the FileSet on days that the 'Full'
> backup set is to be run and restart the bacula-dir daemon prior to the
> time.
>
> That behavior affects changes to the FileSet whether they are Include or
> Exclude selectors.
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
