From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup] docs: s3: extend recommendations and limitations for local cache
Date: Thu, 31 Jul 2025 09:09:45 +0200 [thread overview]
Message-ID: <20250731070945.34344-1-c.ebner@proxmox.com> (raw)
Specify that the local cache must be a dedicated storage, it cannot
reuse pre-existing datastores. Further, give some more
recommendations about size and clarify that storage backed by
volatile memory cannot be used for this, at least for the time being.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
docs/storage.rst | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/docs/storage.rst b/docs/storage.rst
index ef6eb7657..54540219b 100644
--- a/docs/storage.rst
+++ b/docs/storage.rst
@@ -288,11 +288,14 @@ To list your s3 endpoint configuration, run:
# proxmox-backup-manager s3 endpoint list
A new datastore with S3 backend can be created using one of the configured S3 endpoints. Although
-storing all contents on the S3 object store, the datastore requires nevertheless a local cache store,
-used to increase performance and reduce the number of requests to the backend. For this, a local
-filesystem path has to be provided during datastore creation, just like for regular datastore setup.
-A minimum size of a few GiB of storage is recommended, given that cache datastore contents include
-also data chunks.
+storing all contents on the S3 object store, the datastore requires nevertheless a local persisant
+cache, used to increase performance and reduce the number of requests to the backend. For this, a
+local filesystem path has to be provided during datastore creation, just like for regular datastore
+setup. However, unlike for regular datastores the size of the local cache can be limited, 64 GiB to
+128 GiB are recommended given that cached datastore contents include also data chunks. Best is to
+use a dedicated disk, partition or ZFS dataset with quota as local cache. Note however, it is not
+possible to use a pre-existing regular datastore for this. Further, the use of volatile memory only
+for the cache is currently not possible.
To setup a new datastore called ``my-s3-store`` placed in a bucket called ``pbs-s3-bucket``, run:
--
2.47.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-07-31 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 7:09 Christian Ebner [this message]
2025-07-31 10:18 ` [pbs-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250731070945.34344-1-c.ebner@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox