all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 2/2] docs: add table listing possible change detection modes
Date: Mon, 10 Jun 2024 11:53:00 +0200	[thread overview]
Message-ID: <1718013133.7hywqjzcy7.astroid@yuna.none> (raw)
In-Reply-To: <20240607131251.418126-2-c.ebner@proxmox.com>

On June 7, 2024 3:12 pm, Christian Ebner wrote:
> Quick and concise listing of the available change detection modes for
> reference.
> 
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
>  docs/backup-client.rst | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/docs/backup-client.rst b/docs/backup-client.rst
> index e541c5537..e56e0625b 100644
> --- a/docs/backup-client.rst
> +++ b/docs/backup-client.rst
> @@ -320,6 +320,18 @@ the previous backup snapshot. Since the file might only partially re-use chunks
>  to re-use or re-encode the currently cached entries is postponed to when enough
>  information is available, comparing the possible padding to a threshold value.
>  
> +.. _client_change_detection_mode_table:
> +
> +============ ===================================================================
> +Mode         Description
> +============ ===================================================================
> +``legacy``   (current default): Encode all files into a self contained pxar
> +             archive.
> +``data``     Encode all files into a split data and metadata pxar archive.
> +``metadata`` Encode changed files, reuse unchanged from previous snapshot,
> +             creating a split archive.
> +============ ===================================================================
> +
>  The following shows an example for the client invocation with the `metadata`
>  mode:
>  
> -- 
> 2.39.2
> 
> 
> 
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
> 
> 
> 


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  reply	other threads:[~2024-06-10  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 13:12 [pbs-devel] [PATCH proxmox-backup 1/2] client: backup spec: rename change detection mode default Christian Ebner
2024-06-07 13:12 ` [pbs-devel] [PATCH proxmox-backup 2/2] docs: add table listing possible change detection modes Christian Ebner
2024-06-10  9:53   ` Fabian Grünbichler [this message]
2024-06-10  9:52 ` [pbs-devel] applied: [PATCH proxmox-backup 1/2] client: backup spec: rename change detection mode default Fabian Grünbichler

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=1718013133.7hywqjzcy7.astroid@yuna.none \
    --to=f.gruenbichler@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal