From: Christian Ebner <c.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH 0/7] client: add scheduled backup jobs
Date: Thu, 22 Oct 2026 14:58:44 +0200 [thread overview]
Message-ID: <9809fd7b-f21a-4df0-bb6c-5bba0f7ecad4@proxmox.com> (raw)
In-Reply-To: <20261014105208.2747208-1-t.lamprecht@proxmox.com>
On 10/21/26 10:55 PM, Thomas Lamprecht wrote:
> This adds per-user backup jobs and a scheduler daemon to
> proxmox-backup-client, so that a workstation or laptop can back itself
> up on a schedule without a cron entry or systemd timer per job.
>
> A config entry stores everything a backup job run needs: the repository, the
> backup sources and options, where the password and key passphrase come from,
> and an optional pre-run hook that can skip a run, for example on low
> battery.
> The new `job` subcommands manage the jobs in the user's XDG config
> directory, `job run` runs one right away, and `job scheduler` acts as
> daemon-process that runs jobs as they become due. The scheduler is meant
> to run as the systemd user service that the package ships but does not
> enable.
>
> Like the server's jobs, a failed or interrupted run is not retried before
> its next scheduled time. A retry policy could be added later though if it
> turns out to be useful.
Thanks for the patches, really nice addition to the client!
While skimming trough the patches a few ideas for potential improvements
came to mind.
* Allowing to clone an already existing backup job: This would help to
ease setup for multiple jobs with recurring patterns, e.g. only
differing in namespace and backup specs.
* Adding a connection test for a configured job: It is currently
possible to setup a job with incorrect connection information for the
PBS. I think it would be nice to have a command to perform a basic
connection test without having to actually perform a backup run right away.
* Splitting of the target config from the job config: It might make
sense to have the target configurable independent of the job. And make
it reusable for all the client commands not just the jobs itself.
Although not so sure about this part, having all the config in the same
place has advantages as well, and there will mostly be only a single target.
prev parent reply other threads:[~2026-10-22 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 10:51 [PATCH 0/7] client: add scheduled backup jobs Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 1/7] client: backup specification: widen BackupDetectionMode derives Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 2/7] client: job: add backup job config and state types Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 3/7] client: job: add job runner and scheduled backup daemon Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 4/7] client: job: add job management CLI subcommands Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 5/7] client: job: ship systemd user unit for the scheduler Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 6/7] client: job: add battery-check example pre-run hook Thomas Lamprecht
2026-10-14 10:51 ` [PATCH 7/7] docs: client: document scheduled backup jobs Thomas Lamprecht
2026-10-22 12:58 ` Christian Ebner [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=9809fd7b-f21a-4df0-bb6c-5bba0f7ecad4@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.