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 134531FF09C for ; Mon, 02 Nov 2026 00:22:56 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9011321795; Mon, 02 Nov 2026 00:22:17 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH guest-common,manager,docs 0/5] backup jobs: add a start window Date: Mon, 2 Nov 2026 00:20:23 +0100 Message-ID: <20261101232205.976807-1-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793575330102 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.372 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: M73PD3G5RBLYCEDXKJRU2DJ6TNUKZS75 X-Message-ID-Hash: M73PD3G5RBLYCEDXKJRU2DJ6TNUKZS75 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: A backup job can run into business hours, for example when it has to wait for other jobs first or backing up its guests takes longer than planned, and nothing stops it from starting further guest backups then. The new 'start-window' job option sets how many minutes after the scheduled start guest backups may still begin. Running guest backups finish, and guests not started in time are reported as skipped. The window also bounds waiting for the global lock and for backup slots. It counts from the scheduled time, so a missed run repeated later only gets what is left of it. This applies on top of the series "parallel guest backups and backup concurrency limits" [0]. [0]: https://lore.proxmox.com/pve-devel/20261101225849.884587-1-t.lamprecht@proxmox.com/ Repo (build-)dependencies: pve-manager -> pve-guest-common pve-guest-common must be released first, see the note on patch 3. pve-guest-common: Thomas Lamprecht (1): vzdump: add option to stop starting guest backups after a time window src/PVE/VZDump/Common.pm | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) pve-manager: Thomas Lamprecht (3): jobs: pass scheduled run time to job plugins vzdump: honor start window for guest backups ui: backup job: add start window option PVE/API2/Backup.pm | 2 +- PVE/API2/VZDump.pm | 18 ++++++-- PVE/Jobs.pm | 2 +- PVE/Jobs/VZDump.pm | 3 +- PVE/VZDump.pm | 51 +++++++++++++++++---- www/manager6/panel/BackupAdvancedOptions.js | 21 +++++++++ 6 files changed, 81 insertions(+), 16 deletions(-) pve-docs: Thomas Lamprecht (1): vzdump: document the start window vzdump.adoc | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) -- 2.47.3