From: Thomas Lamprecht <t.lamprecht@proxmox.com>
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 [thread overview]
Message-ID: <20261101232205.976807-1-t.lamprecht@proxmox.com> (raw)
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
next reply other threads:[~2026-11-01 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:20 Thomas Lamprecht [this message]
2026-11-01 23:20 ` [PATCH guest-common 1/5] vzdump: add option to stop starting guest backups after a time window Thomas Lamprecht
2026-11-01 23:20 ` [PATCH manager 2/5] jobs: pass scheduled run time to job plugins Thomas Lamprecht
2026-11-01 23:20 ` [PATCH manager 3/5] vzdump: honor start window for guest backups Thomas Lamprecht
2026-11-01 23:20 ` [PATCH manager 4/5] ui: backup job: add start window option Thomas Lamprecht
2026-11-01 23:20 ` [PATCH docs 5/5] vzdump: document the start window Thomas Lamprecht
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=20261101232205.976807-1-t.lamprecht@proxmox.com \
--to=t.lamprecht@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