Re: Force incremental to resume from where it left off

Bill Arlofski via Bacula-users <[email protected]> Fri, 08 Nov 2024 15:53:42 +0000
Newsgroups	gmane.comp.bacula.user
Message-ID	<[email protected]>
On 11/8/24 6:44 AM, 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 !
> 
> Sam
> 

Hello Sam,

Try:
----8<----
* estimate level=Incremental job=xxxx
----8<----

If you do not specify the level for the estimate command, the default is `Full`.

ALSO... you may still have issues as I do not fully know the condition of your Bacula catalog database. You wrote:

`some fileset configs may have change a little bit but for me it was not a real issue`

But to Bacula, this *can* be an issue, and Bacula will err on the side of caution, most likely performing a Full (upgrading 
to a full and logging this as a notice in the job log) if what it sees in your configs does not align with what it knows 
about the Client/Job/Fileset in the DB. ;)

The `IgnoreFileSetChanges = yes` might help, and would be recommended in this case, but there is no way to tell without 
testing the estimate command as above.

Also, Bacula will not "restart" an incremental where it left off unless you had issues the `stop ` command, causing the job 
to be listed as `Incomplete` in the catalog, and then to resume it "from where it left off" you would need to issue the 
`resume incomplete` or `restart incomplete` command. But, this scenario does not seem to be the case here.

So, if Bacula likes your current configs, the best you can hope for is that running an Incremental backs up everything that 
has changed since the last OK backup job.


Hope this helps,
Bill

-- 
Bill Arlofski
[email protected]

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
signature.asc (application/pgp-signature, 509 B)