The number of things I like about Bareos are numerous. But perhaps the
sharpest pinch point that we have with Bareos is the safety feature that
any change to a FileSet causes a full backup to be triggered.
From the docs:
Any change to the list of the included files will cause Bareos to
> automatically create a new FileSet (defined by the name and an MD5
> checksum of the Include/Exclude contents). Each time a new FileSet is
> created, Bareos will ensure that the next backup is always a Full
> save.
And while I understand the safety aspect of that behavior, for our
moderately large 100+ client configuration we are essentially prevented
from making any changes to the FileSet or facing our next backup window
being disastrously large.
My suggestion is to allow for that safety feature to be turned off. Two
approaches came to mind:
The simple approach of having a configuration knob to simply turn off
the behavior of doing a full backup on a FileSet change. This is perhaps
the easiest and also most dangerous.
The more complicated but less dangerous approach that I came up with
would be to allow users to explicitly version FileSets. You could make
versions integers and anytime the version number increases a full-backup
is kicked off. This would allow admins to decide when a fileset change
warrants such an update.
For us, we end up with excludes spread all over the place. Some are in
our FileSet from the initial setup of Bareos, before I fully understood
the quote from the docs above. Some in an exclude file on the director,
some in exclude files on clients. We did the last two when we realized
that FileSet changes would be so disruptive.
Anyway, an idea to drop in the hopper.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
