public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs] vzdump: add section describing PBS change detection mode
Date: Wed, 10 Jul 2024 16:14:15 +0200	[thread overview]
Message-ID: <1720620621.4lr3r60lqb.astroid@yuna.none> (raw)
In-Reply-To: <20240626081311.45882-1-c.ebner@proxmox.com>

On June 26, 2024 10:13 am, Christian Ebner wrote:
> Add a concise section about what PBS change detection mode is and
> what it affects, including a table with a description of the modes.
> 
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
>  vzdump.adoc | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/vzdump.adoc b/vzdump.adoc
> index 79d4bbc..958ee12 100644
> --- a/vzdump.adoc
> +++ b/vzdump.adoc
> @@ -171,6 +171,30 @@ fleecing image up-front. On a thinly provisioned storage, the fleecing image can
>  grow to the same size as the original image only if the guest re-writes a whole
>  disk while the backup is busy with another disk.
>  
> +CT Change Detection Mode
> +~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +Setting the change detection mode defines the encoding format for the pxar
> +archives and how changed and unchanged files are handled for container backups
> +with Proxmox Backup Server as target.
> +
> +Backups of VMs or to other storage backends are not affected by this setting.
> +
> +There are 3 change detection modes available:
> +
> +[width="100%",cols="<m,4d",options="header"]
> +|===============================================================================
> +| Mode     | Description
> +| Default  | The legacy mode, read and encode all files in a self contained
> +pxar archive with format version 1 being uploaded to the Proxmox Backup Server.

I'd shorten this:

Read and encode all files into a single archive, using the pxar format
version 1.

> +| Data     | (EXPERIMENTAL): Read and encode all files, but split data and
> +metadata into separate streams, using the pxar format version 2.
> +| Metadata | (EXPERIMENTAL): Use the metadata archive of the previous backup
> +run to detect unchanged files and reuse the files data already backed up in the
> +previous backup for the current backup run when possible. Data and metadata are
> +encoded into separate streams, using the pxar format version 2.

Split streams and archive format version 2 like `Data`, but use metadata
archive of previous snapshot (if one exists) to detect unchanged files,
and reuse their data chunks without reading file contents from disk,
whenever possible.

This is easier to parse (I hope) and both explains the difference to
`Data`, and the reason why you'd want to use it ;)

> +|===============================================================================
> +
>  Backup File Names
>  -----------------
>  
> -- 
> 2.39.2
> 
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 
> 


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


  reply	other threads:[~2024-07-10 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  8:13 Christian Ebner
2024-07-10 14:14 ` Fabian Grünbichler [this message]
2024-07-10 14:45 ` 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=1720620621.4lr3r60lqb.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=pve-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