From: Christian Ebner <c.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v3 pve-guest-common 1/4] vzdump: add PBS change detection mode configuration
Date: Fri, 7 Jun 2024 15:33:52 +0200 [thread overview]
Message-ID: <20240607133355.431544-2-c.ebner@proxmox.com> (raw)
In-Reply-To: <20240607133355.431544-1-c.ebner@proxmox.com>
Define the possible modes to be configured in a PBS file change
detection mode.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
changes since version 2:
- s/default/legacy
src/PVE/VZDump/Common.pm | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/PVE/VZDump/Common.pm b/src/PVE/VZDump/Common.pm
index 1539444..e04af8c 100644
--- a/src/PVE/VZDump/Common.pm
+++ b/src/PVE/VZDump/Common.pm
@@ -354,6 +354,14 @@ my $confdesc = {
requires => 'storage',
optional => 1,
},
+ 'pbs-change-detection-mode' => {
+ type => 'string',
+ description => "EXPERIMENTAL: PBS mode used to detect file changes and switch encoding"
+ . " format for container backups.",
+ optional => 1,
+ default => 'legacy',
+ enum => [ 'legacy', 'data', 'metadata' ],
+ },
};
sub get_confdesc {
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-06-07 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 13:33 [pve-devel] [PATCH v3 pve-guest-common pve-container pve-manager 0/4] change-detection-mode for PBS Christian Ebner
2024-06-07 13:33 ` Christian Ebner [this message]
2024-06-07 13:33 ` [pve-devel] [PATCH v3 pve-container 2/4] vzdump: conditionally set PBS change detection mode option Christian Ebner
2024-06-07 13:33 ` [pve-devel] [PATCH v3 pve-manager 3/4] www: advanced backup: add pbs change detection mode selector Christian Ebner
2024-06-07 13:33 ` [pve-devel] [PATCH v3 pve-manager 4/4] vzdump: add pbs-change-detection-mode to config template 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=20240607133355.431544-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox