Manage own borgmatic systemd service and timer
Ship borgmatic.service and borgmatic.timer from the backup role instead of relying on the package-provided units. The units are deployed to /etc/systemd/system (overriding the package units), with a configurable schedule via role defaults. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,10 @@
|
||||
---
|
||||
# Schedule for our own borgmatic.timer (overrides the package-shipped unit).
|
||||
# OnCalendar uses systemd.time(7) syntax. RandomizedDelaySec spreads load so
|
||||
# every host doesn't hit the borg server at the same instant.
|
||||
borgmatic_oncalendar: "*-*-* 03:00:00"
|
||||
borgmatic_randomized_delay_sec: 3h
|
||||
borgmatic_persistent: true
|
||||
|
||||
# Extra flags passed to the borgmatic invocation in our borgmatic.service.
|
||||
borgmatic_verbosity_args: "--verbosity -1 --syslog-verbosity 1"
|
||||
Reference in New Issue
Block a user