> Hi, > > After fine-tuning the definition of a Fileset resource (adding a directory > exclusion), I omitted to enable the 'Ignore Fileset Changes' setting. > Obviously, the corresponding next incremental backup got promoted to a > full > one, which I cancelled. > > However, enabling 'Ignore Fileset Changes' the next day did not prevent > the > backup job to be promoted to a full one again. Even less intuitively, > reverting the fileset definition to its original state did not stop the > backup job from being promoted. The latter remained true, whether or not > 'ignore fileset changes' was enabled. > > All initiated full backups were cancelled. The corresponding job resource > did not have its 'rerun failed levels' setting set to 'yes'. > > Did some sort of 'fileset has changed' flag get set in a data structure > somewhere, that I could manually change to continue running incremental > backups? >
It appeared that instead of a simple flag, the director uses an MD5 hash of the fileset definitions which it stores in the FileSet database, which it creates only if 'ignore fileset changes' is set to no (and upon the first full backup of a fileset, obviously). That hash is compared to the state of the fileset before every non-full backup job. Deleting the last entry there caused Bacula to consider my FileSet as the newest version again, and thus to continue doing incremental updates. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
