mirror of
https://github.com/borgbackup/borg.git
synced 2025-02-23 14:41:43 +00:00
docs: point out tuning options for borg create, fixes #3239
This commit is contained in:
parent
4835dce913
commit
520a6a2ef1
1 changed files with 6 additions and 0 deletions
|
@ -2761,6 +2761,12 @@ def define_archive_filters_group(subparser, *, sort_by=True, first_last=True):
|
|||
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.
|
||||
|
|
Loading…
Reference in a new issue