Re: Force incremental to resume from where it left off
Phil Stracchino <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Organization | Fenian House Publishing |
| Message-ID | <[email protected]> |
On 11/8/24 08:44, Samuel Zaslavsky wrote: > 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 ! It stands mentioning that the critical weak point of any incremental-forever scheme is that if a single incremental backup becomes unavailable for any reason, you may be unable to restore your data. Bacula's "virtual full" model exists, in part, to try to *reduce* the risk of this happening. -- Phil Stracchino Fenian House Publishing [email protected] [email protected] Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users