aboutsummaryrefslogtreecommitdiffstats
path: root/templates
Commit message (Collapse)AuthorAgeFilesLines
* Add option to configure SuccessExitStatusv1.0.5Colin Wilk6 days1-1/+3
| | | | | | | | Useful for letting systemd services not get marked as failed state when borg throws warnings. Keeping default to only accept exit code 0 as a successful state. Related: PR #2 https://github.com/kliwniloc/ansible-role-borgbackup/pull/2
* fix: systemd SuccessExitStatus to accept warning exit as successIgnacio Garcia6 days1-0/+1
|
* Migrate role from cron to systemdColin Wilk2023-11-042-0/+23
Systemd gives us the ability to monitor backup job status using existing monitoring solutions (node exporter) and allows us greater control over the scheduling of the backup jobs. This introduces a breaking change that requires users to manually remove the old repositories from the clients and redeploying them with the role. You will have to remove the Cron job that was created by the Ansible script, everything else will be overwritten with a run from the newer version. - name: Remove backup cron jobs ansible.builtin.cron: name: BORG (Application level backups) state: absent become: true - name: Remove env for backup cron job ansible.builtin.cron: name: BORG_PASSPHRASE env: true state: absent become: true Performing manual migrations on the Borg server is not required. We now additionally support multiple Borg repositories per client host using the `borg_backup_argument` variable. Signed-off-by: Colin Wilk <colin.wilk@tum.de>