system-config/playbooks/roles/borg-backup
Ian Wienand 8c9ba67296 borg-backup: save PIPESTATUS before referencing
It's not obvious, but the if statements can change the PIPESTATUS
meaning we're not matching what we think we're matching.  Save the
pipestatus of the backup commands so we exit the backup script with
the right code.

Change-Id: I83c7db45d3622067eb05107e26fbdc7a8aeecf63
2021-02-09 16:22:32 +11:00
..
defaults borg-backup: add a few more global excludes 2021-02-05 11:47:47 +11:00
tasks borg-backup: fix logrotate name 2021-01-20 16:03:46 +11:00
templates borg-backup: save PIPESTATUS before referencing 2021-02-09 16:22:32 +11:00
README.rst borg-backup: implement saving a stream, use for database backups 2021-02-03 11:43:12 +11:00

README.rst

Configure a host to be backed up

This role setups a host to use borgp for backup to any hosts in the borg-backup-server group.

A separate ssh key will be generated for root to connect to the backup server(s) and the host key for the backup servers will be accepted to the host.

The borg tool is installed and a cron job is setup to run the backup periodically.

Note the borg-backup-server role must run after this to create the user correctly on the backup server. This role sets a tuple borg_user with the username and public key; the borg-backup-server role uses this variable for each host in the borg-backup group to initalise users.

Hosts can place into /etc/borg-streams which should be a script that outputs to stdout data to be fed into a backup archive on each run. This will be saved to an archive with the name of the file. This is useful for raw database dumps which allow borg to deduplicate as much as possible.

Role Variables

The username to connect to the backup server. If this is left undefined, it will be automatically set to borg-$(hostname)