Scheduling backups
Set up recurring backups through systemd timers from the Schedule screen.
Last updated: May 18, 2026
The Schedule screen (key 4) sets up recurring backups. Instead of starting each backup by hand, you define a frequency and the host takes care of it on its own.
The frequencies on offer
The screen offers ready-made schedules:
| Preset | Frequency |
|---|---|
| Hourly | at the start of every hour |
| Daily at 02:00 | every day at 02:00 |
| Daily at 23:00 | every day at 23:00 |
| Weekly | on Sunday at 03:00 |
| Monthly | on the 1st of the month at 04:00 |
| Custom | free OnCalendar expression |
The Custom preset accepts a systemd OnCalendar expression, for needs that match no preset.
How it works
Cloud-PBS TUI does not run in the background: it relies on systemd. From the chosen schedule, the screen generates two systemd units:
- a service (
.service) that runs the backup; - a timer (
.timer) that triggers the service at the defined frequency.
Once the schedule is applied, backups happen even when Cloud-PBS TUI is not open: it is systemd that runs them.
Installation level
The schedule can be installed:
- at the user level: timers placed under the current user’s systemd directory;
- at the system level: timers managed by systemd for the whole machine (requires suitable privileges).
The Catch-up option (Persistent) asks systemd to run a missed backup at the next boot, when the machine was off at the scheduled time. A random delay can be added to spread the load.
Apply and disable
The screen lets you apply the schedule (creating and enabling the units) and disable it (removing the units). The current state is recalled at the bottom of the screen.
Next step
To trigger a backup without waiting for the next scheduled run, see Running a backup.