From: Christian Ebner <c.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 pve-docs] vzdump: add section describing PBS change detection mode
Date: Wed, 10 Jul 2024 16:41:57 +0200 [thread overview]
Message-ID: <20240710144157.280353-1-c.ebner@proxmox.com> (raw)
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 9b1cb61..4607e40 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -175,6 +175,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 | 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): Split streams and use 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.
+|===============================================================================
+
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
next reply other threads:[~2024-07-10 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 14:41 Christian Ebner [this message]
2024-07-11 8:24 ` Aaron Lauterer
2024-07-11 8:28 ` Christian Ebner
2024-07-11 9:38 ` 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=20240710144157.280353-1-c.ebner@proxmox.com \
--to=c.ebner@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 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.