From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH] docs: reword WORM tape documentation
Date: Thu, 2 Mar 2023 12:18:03 +0100 [thread overview]
Message-ID: <20230302111803.1036128-1-a.lauterer@proxmox.com> (raw)
Mainly splitting long sentences into smaller ones. Some rewording
happened in the process.
The changes should still transport the same information.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
docs/tape-backup.rst | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/docs/tape-backup.rst b/docs/tape-backup.rst
index a3a62818..f04b1284 100644
--- a/docs/tape-backup.rst
+++ b/docs/tape-backup.rst
@@ -1053,17 +1053,18 @@ This command does the following:
WORM Tapes
----------
-WORM (write once, read many) tapes are special cartridges that cannot be deleted
-or overwritten, which may be useful for legal or protection purposes.
+WORM (write once, read many) tapes are special cartridges that cannot be
+deleted or overwritten. This may be useful for legal or protection purposes.
-Since they cannot be overwritten or deleted, if you want to use them, you must
-use a media pool with a retention policy of `keep`, otherwise a backup job
-potentially fails when trying to erase or overwrite it.
+If you want to use them, you must use a media pool with a retention policy of
+`keep`. Otherwise, a backup job can fail when it tries to erase or overwrite
+the tape.
+
+Proxmox Backup Server makes no distinction between normal and WORM tapes. To
+avoid confusion, use a different naming scheme for WORM backups and use
+dedicated media pools for them. Do not mix WORM and non-WORM tapes in the same
+media pool.
-Proxmox Backup Server does not handle WORM tapes differently, so it is
-recommended to use a different naming scheme, use only seperate media pools
-and not mix WORM and non-WORM tapes in a media pool together (since it may
-lead to confusion about which tapes are not overwritable).
Example Setups
--------------
--
2.30.2
next reply other threads:[~2023-03-02 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 11:18 Aaron Lauterer [this message]
2023-03-27 11:54 ` Dominik Csapak
2023-03-27 12:10 ` [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=20230302111803.1036128-1-a.lauterer@proxmox.com \
--to=a.lauterer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.