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 16C541FF09D for ; Sun, 01 Nov 2026 23:59:16 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 029362166B; Sun, 01 Nov 2026 23:59:13 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH cluster 02/19] datacenter config: backup concurrency: add cluster-wide limit Date: Sun, 1 Nov 2026 23:58:29 +0100 Message-ID: <20261101225849.884587-3-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261101225849.884587-1-t.lamprecht@proxmox.com> References: <20261101225849.884587-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793573947924 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.406 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: X75OFLNPFT2RDKGYJJE2MGSLONQPCGPV X-Message-ID-Hash: X75OFLNPFT2RDKGYJJE2MGSLONQPCGPV X-MailFrom: t.lamprecht@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: Nodes run their part of a backup job on their own, so how many guests are backed up at the same time depends on how many nodes the guests of a job are spread over. In larger clusters this can overload shared storages and backup servers, while lowering the per-node limit to protect them slows down jobs whose guests are mostly on one node. Add an optional limit for the whole cluster, enforced by the backup code of all nodes together. Signed-off-by: Thomas Lamprecht --- src/PVE/DataCenterConfig.pm | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/PVE/DataCenterConfig.pm b/src/PVE/DataCenterConfig.pm index baff829..f6ac5b9 100644 --- a/src/PVE/DataCenterConfig.pm +++ b/src/PVE/DataCenterConfig.pm @@ -229,6 +229,13 @@ my $backup_concurrency_format = { default_key => 1, optional => 1, }, + cluster => { + type => 'integer', + description => + "Maximal number of guests backed up at the same time in the whole cluster.", + minimum => 1, + optional => 1, + }, }; my $u2f_format = { -- 2.47.3