Josip DeanovicOn Tuesday 2021-11-30 10:27:08 wrote: > On Tuesday 2021-11-30 15:29:42 Gary R. Schmidt wrote: > > Also, be aware that you have created a completely new file system, all > > the inodes will be different, and the access/modify/change/birth times > > on all the directories will be set to when the new directory was > > created - i.e. when it started to be populated by the restore. > > > > And everything will have different dev and rdev values. > > The documentation says that Bacula decides what files to backup for > Incremental and Differential backup by comparing the change (st_ctime) > and modification (st_mtime) times of the file to the time the last > backup completed. > > Could it be that the "Accurate" option changes that behavior when used > in the Job resource? > > If that is the case then it could be controlled by the "Accurate" option > used in the FileSet resource.
Just did a simple test. What changes during the restore is the change time (st_ctime). That's why Bacula decides to backup restored files with the next Incremental backup. There is an option "mtimeonly=yes" which could be used in the FileSet. This would solve the problem Neil currently has to deal with. I would suggest to remove that option once it is not needed any more as it could have undesirable effects on the long run. Adding and removing of this option to the FileSet resource will not trigger promotion of Incremental job to Full unless Include or Exclude lists are changed as well. Regards! -- Josip Deanovic _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
