From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 pve-guest-common pve-container pve-manager 0/4] change-detection-mode for PBS
Date: Fri, 07 Jun 2024 12:58:50 +0200 [thread overview]
Message-ID: <1717757784.5yvv7x53m2.astroid@yuna.none> (raw)
In-Reply-To: <20240529120714.253120-1-c.ebner@proxmox.com>
Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
with one slight caveat - I'd like to change the "Default" enum value in
PBS to something else "V1", "Legacy", .., which has some consequences
here, so I held off applying this for now..
On May 29, 2024 2:07 pm, Christian Ebner wrote:
> This patch series defines the vzdump configuration description as well
> as backup job configuration option in the WebUI to set the
> experimental `change-detection-mode` parameter to the
> proxmox-backup-client invocation for container backups having a Proxmox
> Backup Server storage target.
>
> This allows to either set the parameter to the node wide vzdump.conf
> or on a per job level. The following shows an exemplary job
> configuration taken from /etc/pve/jobs.cfg:
>
> ```
> vzdump: backup-ab2edf62-d43c
> schedule yearly
> compress zstd
> enabled 1
> fleecing 0
> mode snapshot
> notes-template {{guestname}}
> pbs-change-detection-mode metadata
> storage pbs-local
> vmid 100
> ```
>
> This patches depend on a proxmox-backup-client compiled with the
> following patch series applied:
> https://lists.proxmox.com/pipermail/pbs-devel/2024-May/009526.html
>
> pve-guest-common:
>
> Christian Ebner (1):
> vzdump: add PBS change detection mode configuration
>
> src/PVE/VZDump/Common.pm | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> pve-container:
>
> Christian Ebner (1):
> vzdump: conditionally set PBS change detection mode option
>
> src/PVE/VZDump/LXC.pm | 2 ++
> 1 file changed, 2 insertions(+)
>
> pve-manager:
>
> Christian Ebner (2):
> www: advanced backup: add pbs change detection mode selector
> vzdump: add pbs-change-detection-mode to config template
>
> configs/vzdump.conf | 1 +
> www/manager6/panel/BackupAdvancedOptions.js | 20 ++++++++++++++++++++
> 2 files changed, 21 insertions(+)
>
> --
> 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
prev parent reply other threads:[~2024-06-07 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 12:07 Christian Ebner
2024-05-29 12:07 ` [pve-devel] [PATCH v2 pve-guest-common 1/4] vzdump: add PBS change detection mode configuration Christian Ebner
2024-05-29 12:07 ` [pve-devel] [PATCH v2 pve-container 2/4] vzdump: conditionally set PBS change detection mode option Christian Ebner
2024-05-29 12:07 ` [pve-devel] [PATCH v2 pve-manager 3/4] www: advanced backup: add pbs change detection mode selector Christian Ebner
2024-05-29 12:07 ` [pve-devel] [PATCH v2 pve-manager 4/4] vzdump: add pbs-change-detection-mode to config template Christian Ebner
2024-06-07 10:58 ` Fabian Grünbichler [this message]
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=1717757784.5yvv7x53m2.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