From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 1/3] docs: tape: replace 'export-media' with 'export-media-set'
Date: Tue, 12 Dec 2023 15:34:23 +0100 [thread overview]
Message-ID: <20231212143425.1844448-1-d.csapak@proxmox.com> (raw)
there is no 'export-media' option, only 'export-media-set'
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
docs/tape-backup.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/tape-backup.rst b/docs/tape-backup.rst
index f54c00b8..cda84a6f 100644
--- a/docs/tape-backup.rst
+++ b/docs/tape-backup.rst
@@ -664,16 +664,16 @@ dust protection than inside a drive:
.. Note:: For failed jobs, the tape remains in the drive.
-For tape libraries, the ``export-media`` option moves all tapes from
+For tape libraries, the ``export-media-set`` option moves all tapes from
the media set to an export slot, making sure that the following backup
cannot use the tapes. An operator can pick up those tapes and move them
to a vault.
.. code-block:: console
- # proxmox-tape backup-job update job2 --export-media
+ # proxmox-tape backup-job update job2 --export-media-set
-.. Note:: The ``export-media`` option can be used to force the start
+.. Note:: The ``export-media-set`` option can be used to force the start
of a new media set, because tapes from the current set are no
longer online.
--
2.30.2
next reply other threads:[~2023-12-12 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:34 Dominik Csapak [this message]
2023-12-12 14:34 ` [pbs-devel] [PATCH proxmox-backup 2/3] docs: tape: document advanced changer options Dominik Csapak
2023-12-12 14:34 ` [pbs-devel] [PATCH proxmox-backup 3/3] docs: tape: add lto 9 considerations Dominik Csapak
2023-12-13 11:28 ` [pbs-devel] applied: [PATCH proxmox-backup 1/3] docs: tape: replace 'export-media' with 'export-media-set' Dietmar Maurer
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=20231212143425.1844448-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