mirror of
https://github.com/borgbackup/borg.git
synced 2026-04-29 18:10:59 -04:00
docs: mention BORG_FILES_CACHE_SUFFIX as alternative to BORG_FILES_CACHE_TTL, fixes #5602
This commit is contained in:
parent
65713d81fe
commit
19f2d274d5
1 changed files with 4 additions and 0 deletions
|
|
@ -1006,6 +1006,10 @@ will be slow because it would chunk all the files each time. If you set
|
|||
BORG_FILES_CACHE_TTL to at least 26 (or maybe even a small multiple of that),
|
||||
it would be much faster.
|
||||
|
||||
Besides using a higher BORG_FILES_CACHE_TTL (which also increases memory usage),
|
||||
there is also BORG_FILES_CACHE_SUFFIX which can be used to have separate (smaller)
|
||||
files caches for each backup set instead of the default one (big) unified files cache.
|
||||
|
||||
Another possible reason is that files don't always have the same path, for
|
||||
example if you mount a filesystem without stable mount points for each backup or if you are running the backup from a filesystem snapshot whose name is not stable.
|
||||
If the directory where you mount a filesystem is different every time,
|
||||
|
|
|
|||
Loading…
Reference in a new issue