systemd’s `AccuracySec` is mainly there in order to allow it to coalescing
wake-ups for multiple timers.
It’s default of `1min` minute should be enough for this.
Using its `RandomizedDelaySec` in order to spread load from e.g. multiple
sources that would all perform backups to one target, wouldn’t really make much
sense either.
Either, the value would need to be quite large, thereby making backups/snapshots
too wobbly, or it wouldn’t be effective as at least the backups typically take
quite some time.
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
It does not make sense for the timer or the service to be started (the latter
when done so manually) when neither of the two default config files exists.
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
btrbk supports hourly backups, so it makes sense for the timer to run hourly,
too.
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Using `WantedBy=multi-user.target` makes boot wait for btrbk.service
before it's considered "finished". This can be checked by running
`systemd-analyze` or checking the system log using `journalctl`.
Timers should use the "timers.target" target, see systemd.special(7).
Christoph Anton Mitterer