systemd timer
A scheduled-task mechanism provided by systemd, consisting of paired .timer and .service units; it supports viewing the next trigger time and running missed tasks, with output routed uniformly to the journal.
Timeline (last 90 days)
The backup job is driven by a systemd timer, which invokes the /opt/orqestra/scripts/backup-db.sh script every day at 5:30 via orqestra-backup.timer.
When the task chain is "systemd timer → shell script → restic → B2," the failure can occur at any link in the chain, and reporting only a line number amounts to shifting the entire localization cost onto the person receiving the alert.
A systemd timer is the scheduled task mechanism provided by systemd, consisting of a pair of units: the .timer unit defines the trigger time (similar to cron), and the .service unit defines the command actually executed.
Improvement principle: when a restic job runs under a systemd timer via a script, the alert should carry restic's own error output, because a line number plus a status word is insufficient to support any action.
A systemd timer consists of two files: a .timer unit (which defines the trigger time) and a .service unit (which defines the command to execute).
Advantages of systemd timers over cron include unified collection of execution logs into journald, support for OnFailure= to trigger another unit when a task fails, and the ability to set Persistent=true so that tasks missed during a shutdown are run after the next boot.
All Facts (6)
The backup job is driven by a systemd timer, which invokes the /opt/orqestra/scripts/backup-db.sh script every day at 5:30 via orqestra-backup.timer.
50%UnverifiedWhen the task chain is "systemd timer → shell script → restic → B2," the failure can occur at any link in the chain, and reporting only a line number amounts to shifting the entire localization cost onto the person receiving the alert.
50%UnverifiedA systemd timer is the scheduled task mechanism provided by systemd, consisting of a pair of units: the .timer unit defines the trigger time (similar to cron), and the .service unit defines the command actually executed.
50%UnverifiedImprovement principle: when a restic job runs under a systemd timer via a script, the alert should carry restic's own error output, because a line number plus a status word is insufficient to support any action.
50%UnverifiedA systemd timer consists of two files: a .timer unit (which defines the trigger time) and a .service unit (which defines the command to execute).
50%UnverifiedAdvantages of systemd timers over cron include unified collection of execution logs into journald, support for OnFailure= to trigger another unit when a task fails, and the ability to set Persistent=true so that tasks missed during a shutdown are run after the next boot.
50%