On 2024-09-26 13:02, Marco Gaiarin wrote:
Hello Marco!
Or it is still the 'fileset change' the trigger, so scripts can make
all the
dumbest things, but bacula keep going on incrementals?
Also, if my script mount on '/some/dirs-202040926' and pass this as a
backup
dir for a full, but tomorrow script mount '/some/dirs-202040927' and
calls
for an incremental on that, i think will make still a new full...
Unless the "Ignore FileSet Change" option is used, Bacula will compare
the MD5
checksum of the Include/Exclude contents of the FileSet and decide
whether a
Full backup is needed or not.
I don't recommend using this option and the Bacula documentation
strongly
recommends against it as well because it bears a risk of having
incomplete
backup.
Seems to me there's no (easy) escape, and i need to mount snapshots on
the
same mountpoint to have working incrementals...
Consistency is always desired. :-)
In your case, you are trying to devise a versioning by creating new
directories
named by the date but it might be unnecessary as Bacula already keeps
that
information for you.
For example, while browsing/restoring backup of the specific date, you
would
get the state of a backed up directory as it was during the execution of
a
selected backup job.
I would recommend the "accurate" option in this case.
If you cannot avoid creation of the directories based on the date, you
might
help yourself by using bind mount option of the mount(8).
Regards
--
Josip Deanovic
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
