From 9f09a9e0964f8164241dbe1383f438176dca6625 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Sat, 30 Apr 2022 20:28:46 +0200 Subject: [PATCH] docs: mention BORG_FILES_CACHE_SUFFIX as alternative to BORG_FILES_CACHE_TTL, fixes #5602 --- docs/faq.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index 8ef1b82aa..b500ae469 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -1080,6 +1080,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