Just to be sure, are you setting level=Incremental in the estimate command?
Are there any messages in bconsole after running the estimate command (use the messages command to check)? In particular, look for "The FileSet ... was modified on ..." or "No prior or suitable Full backup found..." Did you run estimate (or a backup) before adding Ignore FileSet Changes = yes in the FileSet? What is the output of the following sql command? select * from fileset where fileset='...your fileset name...' order by CreateTime desc; __Martin >>>>> On Fri, 8 Nov 2024 14:44:43 +0100, Samuel Zaslavsky said: > > Hello everyone, > > I have a job backing up several hundreds of To. > Job is incremental, every week, so only hundreds of Go, or a few To every > week. > After bad manipulation ( I know, I know...), we lost the bacula > configurations (jobs, fileset, etc.) *but not the database*. > > So we reinstalled bacula, connected it to the old database, recreated Jobs > and filesets etc. > Quite a quick and easy task. In Baculum, everything seems to be back as > before. > > Of course, some fileset configs may have change a little bit but for me it > was not a real issue : I just want the job to backup new files, that's all. > Also I added Ignore FileSet Changes = yes in the FileSet, to be sure it > would not start a new full backup... > > So I was expecting it would "go on" as if nothing happened. > But when I do an estimate, Bacula seems to be wanting to do a brand new > full backup. > This is very annoying, since it would take months, dozens of tapes, etc. > > I would like Bacula to resume at the point where it left off. > > Anyone knows how to achieve that ? > > Thanks a lot for your help ! > > Sam > > > > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
