public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 3/3] docs: add WORM tape documentation
Date: Thu, 23 Feb 2023 12:59:02 +0100	[thread overview]
Message-ID: <20230223115902.1180695-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20230223115902.1180695-1-d.csapak@proxmox.com>

a short section about how to use WORM tapes (since we currently don't
handle them differently than normal tapes)

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 docs/tape-backup.rst | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/tape-backup.rst b/docs/tape-backup.rst
index fbc72b67..a3a62818 100644
--- a/docs/tape-backup.rst
+++ b/docs/tape-backup.rst
@@ -1050,6 +1050,21 @@ This command does the following:
 
 - unload the cleaning tape (to slot 3)
 
+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.
+
+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.
+
+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





      parent reply	other threads:[~2023-02-23 11:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 11:59 [pbs-devel] [PATCH proxmox-backup 1/3] tape: inventory: don't skip unassigned tapes completely Dominik Csapak
2023-02-23 11:59 ` [pbs-devel] [PATCH proxmox-backup 2/3] tape: initial WORM support Dominik Csapak
2023-02-28  9:56   ` Dietmar Maurer
2023-02-23 11:59 ` Dominik Csapak [this message]

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=20230223115902.1180695-3-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal