systemd based backup schedules for restic with per-instance config files
- Configuration file for each backup task stored in
/etc/restic/<task>.conf - Invoke restic via systemd service instance
- Backup operation executed as unprivileged user via linux capabilities
CAP_DAC_READ_SEARCH - Monthly data cleanup (forget+prune) and integrity check
- systemd
[email protected]to run the backup - systemd
[email protected]to apply the data retention policy (restic forget --prune) and run backup integrity check - send backup logs (from journald) via taskrunner to custom http endpoint (optional)
apt-get install restic-scheduler
- Copy the files of
systemd/to/lib/systemd/system - Create backup user
restic - Create config path
/etc/restic - Create cache path
/var/cache/restic
restic-scheduler comes with a systemd service and timer. You can easily modify the scripts to match your needs (backup schedule, config path).
The service file is designed to work on per-instance base and uses the instance name as config file name /etc/restic/%I.conf.
All options of the config file are exposed as environment variables for the restic process - you can use any supported env vars.
Configuration
File: /etc/restic/<mybackup>.conf
## full support for restic env vars
# @see https://restic.readthedocs.io/en/latest/040_backup.html#environment-variables
## repository address
# @env
RESTIC_REPOSITORY="sftp:myhost.example.org:/backupdir"
## repository password provided via file
# @env
RESTIC_PASSWORD_FILE="/etc/restic/repo.key"
## additional args
# @restic-scheduler.service
BACKUP_ARGS="--exclude-if-present .nobackup --exclude-file /etc/restic/exclude.list"
## paths to be included in the snapshot
# @restic-scheduler.service
BACKUP_PATHS="/opt /srv /home"
Enable schedule
systemctl enable [email protected] --nowsystemd files
/lib/systemd/system/[email protected]/lib/systemd/system/[email protected]
restic allows an easy setup of data rentention policies regarding a predefined schedule. restic-scheduler supports the time-based schemes via config file.
To use other schemes you can override the systemd file (drop in) or create a custom systemd service.
The service file is designed to work on per-instance base and uses the instance name as config file name /etc/restic/%I.conf
Note: for security reasons, the policy --keep-last is set to 10!
Configuration
File: /etc/restic/<mybackup>.conf
# @restic-retention.service
RETENTION_POLICY_DAYS=14
RETENTION_POLICY_WEEKS=12
RETENTION_POLICY_MONTHS=18
RETENTION_POLICY_YEARS=2
## additional arguments
# @restic-retention.service
RETENTION_ARGS=""
## data validation (restic check)
# ---------------------------------
## additional arguments
# @restic-retention.service
VALIDATION_ARGS=""
Enable schedule
systemctl enable [email protected] --nowDefaults
/lib/systemd/system/[email protected]/lib/systemd/system/[email protected]
Sometime it's useful to receive backup logs via e-mail or push-notification without the requirement of a central syslog service. restic-scheduler comes with support for taskrunner to log job outputs via a custom http endpoint.
In case of restic-scheduler, an additional systemd service is invoked which extracts the log output from journald as well as start/stop timestamps and the exit code.
Enable log transmission
systemctl enable [email protected] --now
systemctl enable [email protected] --nowDefaults
/lib/systemd/system/[email protected]/lib/systemd/system/[email protected]
The .deb package is automatically generated via a Continuous Delivery Pipeline - please do not build packages manually!
restic-scheduler is OpenSource and licensed under the Terms of Mozilla Public License 2.0. You're welcome to contribute