From 3bdf1193ad50ae2c44ea0b54655a8984bfe9f5bd Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Sat, 25 Nov 2017 15:21:43 +0100 Subject: [PATCH] docs: point out tuning options for borg create, fixes #3239 (cherry picked from commit 520a6a2ef116331964a57e857d32ff217b14fb5d) --- src/borg/archiver.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/borg/archiver.py b/src/borg/archiver.py index fdeaec0f9..6f372e731 100644 --- a/src/borg/archiver.py +++ b/src/borg/archiver.py @@ -2916,6 +2916,12 @@ class Archiver: it had before a content change happened. This can be used maliciously as well as well-meant, but in both cases mtime based cache modes can be problematic. + By default, borg tries to archive all metadata that it supports archiving. + If that is not what you want or need, there are some tuning options: + + - --nobsdflags (getting bsdflags has a speed penalty under Linux) + - --noatime (if atime changes frequently, the metadata stream will dedup badly) + The mount points of filesystems or filesystem snapshots should be the same for every creation of a new archive to ensure fast operation. This is because the file cache that is used to determine changed files quickly uses absolute filenames.