mirror
/
borg
mirror of https://github.com/borgbackup/borg.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #3367 from ThomasWaldmann/create-tuning-options-1.1 

docs: point out tuning options for borg create, fixes #3239
This commit is contained in:
TW 2017-11-25 15:27:37 +01:00 committed by GitHub
parent 4021423330 3bdf1193ad
commit 960c78ffea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/borg/archiver.py
View File

@ -2916,6 +2916,12 @@ class Archiver:
it had before a content change happened. This can be used maliciously as well as 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. 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 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 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. is used to determine changed files quickly uses absolute filenames.