On 06/01/17 10:06, Jörg Steffens wrote:
On 01.06.2017 at 16:48 wrote Douglas K. Rand:
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.
Already there, see
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirFileSetIgnore%20File%20Set%20Changes
Ohh, that is embarrassing. I have read those docs from one end to the
other, but clearly my selective memory prevented me from recalling that
very important detail.
Thanks for the tip!
And sorry for the noise.
Blush.
--
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.
