From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id D53D81FF09C for ; Mon, 02 Nov 2026 12:59:55 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 859DF2171B; Mon, 02 Nov 2026 12:59:53 +0100 (CET) From: Jakob Klocker To: pve-devel@lists.proxmox.com Subject: [PATCH pve-guest-common 1/3] vzdump: add error-behavior and max-retries options Date: Mon, 2 Nov 2026 12:58:49 +0100 Message-ID: <20261102115851.171429-2-j.klocker@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261102115851.171429-1-j.klocker@proxmox.com> References: <20261102115851.171429-1-j.klocker@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793620790058 X-SPAM-LEVEL: Spam detection results: 0 AWL 1.488 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: XLKRURDAPMLFLU5VKPRGVQIM5IH3ZJCG X-Message-ID-Hash: XLKRURDAPMLFLU5VKPRGVQIM5IH3ZJCG X-MailFrom: j.klocker@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Add two new backup job options to control what happens when a guest backup fails: - 'error-behavior' selects the behavior. 'ignore' keeps the current behavior and is the default. 'retry' queues the failed guest and retries it after the remaining guests have been backed up. 'retry-immediately' retries the failed guest right away, before continuing with the next one. - 'max-retries' limits how many times a failed guest backup is retried (1-10, default 5). Signed-off-by: Jakob Klocker --- src/PVE/VZDump/Common.pm | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/PVE/VZDump/Common.pm b/src/PVE/VZDump/Common.pm index 67a4cf4..42139ae 100644 --- a/src/PVE/VZDump/Common.pm +++ b/src/PVE/VZDump/Common.pm @@ -383,6 +383,21 @@ my $confdesc = { optional => 1, enum => ['legacy', 'data', 'metadata'], }, + 'error-behavior' => { + type => 'string', + description => "Behavior when a guest backup fails.", + enum => ['ignore', 'retry', 'retry-immediately'], + optional => 1, + default => 'ignore', + }, + 'max-retries' => { + type => 'integer', + description => "Maximum number of times to retry a failed guest backup.", + minimum => 1, + maximum => 10, + optional => 1, + default => 5, + }, }; sub get_confdesc { -- 2.47.3