From: Gabriel Goller <g.goller@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] docs: client: mention missing catalog for split archives
Date: Tue, 16 Jul 2024 10:44:19 +0200 [thread overview]
Message-ID: <20240716084419.wn5olg5x2dgw2dhs@luna.proxmox.com> (raw)
In-Reply-To: <20240715144244.141653-1-c.ebner@proxmox.com>
On 15.07.2024 16:42, Christian Ebner wrote:
>Adds a note informing the users that the catalog is not encoded for
>change detection modes set to `data` or `metadata`, and mention to
>mount the snapshot archive as alternative for inspecting the content.
>
>Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>---
> docs/backup-client.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
>diff --git a/docs/backup-client.rst b/docs/backup-client.rst
>index e56e0625b..ca054a762 100644
>--- a/docs/backup-client.rst
>+++ b/docs/backup-client.rst
>@@ -339,6 +339,13 @@ mode:
>
> # proxmox-backup-client backup.pxar:./linux --change-detection-mode=metadata
>
>+.. Note:: Backup snapshots create with ``change-detection-mode`` set to ``data``
s/create/created/
>+ or ``metadata`` do not encode a dedicated catalog, as the metadata archive
>+ already contains the same information in a quickly accessible manner.
>+ Therefore, the ``proxmox-backup-client catalog`` commands are not available
>+ for these snapshots, ``proxmox-backup-client mount`` can be used instead to
^
maybe insert 'and' instead of the comma?
>+ mount and inspect these snapshots.
^
s/these snapshots/them/
>+
> .. _client_encryption:
>
> Encryption
Otherwise LGTM!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-07-16 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:42 Christian Ebner
2024-07-16 8:44 ` Gabriel Goller [this message]
2024-07-16 9:07 ` Christian Ebner
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=20240716084419.wn5olg5x2dgw2dhs@luna.proxmox.com \
--to=g.goller@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.