From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup] docs: add note for not using remote storages
Date: Tue, 11 Jun 2024 11:30:46 +0200 [thread overview]
Message-ID: <20240611093046.1092265-1-d.csapak@proxmox.com> (raw)
such as NFS or SMB. They will not provide the expected performance
and it's better to recommend against them.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
if we want to discourage users even more, we could also detect it on
datastore creation and put a warning into the task log
also if we ever come around to implementing the 'health' page thomas
wished for, we can put a warning/error there too
docs/system-requirements.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/docs/system-requirements.rst b/docs/system-requirements.rst
index fb920865..17756b7b 100644
--- a/docs/system-requirements.rst
+++ b/docs/system-requirements.rst
@@ -41,6 +41,9 @@ Recommended Server System Requirements
* Use only SSDs, for best results
* If HDDs are used: Using a metadata cache is highly recommended, for example,
add a ZFS :ref:`special device mirror <local_zfs_special_device>`.
+ * While it's technically possible to use remote storages such as NFS or SMB,
+ the additional latency and overhead drastically reduces performance and it's
+ not recommended to use such a setup.
* Redundant Multi-GBit/s network interface cards (NICs)
--
2.39.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2024-06-11 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 9:30 Dominik Csapak [this message]
2024-06-11 9:42 ` [pbs-devel] applied: " Dietmar Maurer
2024-06-11 18:05 ` [pbs-devel] " Thomas Lamprecht
2024-06-12 6:39 ` Dominik Csapak
2024-06-12 15:40 ` Thomas Lamprecht
2024-06-13 8:02 ` Dominik Csapak
2024-06-17 15:58 ` 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=20240611093046.1092265-1-d.csapak@proxmox.com \
--to=d.csapak@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