3efcc957d6
On our zuul-scheduler host the /root/.bup dir is extremely large. On closer examination this appears to be due to large file indexes. Looking at the host we've noticed that we are backing up the status.json backups as well as job runtime files which can and do change frequently which could lead to very large file indexes. We don't actually need to back these up permanently so exclude them from bup's list. the /var/lib/zuul/backup dir contains status.json backups which are really only useful in the immediate time frame and the times db is something we can live without if we lose it (we'll just build a new one). Change-Id: Id3029eec3a6478c496712876b9ec753029313efa |
||
|---|---|---|
| .. | ||
| files | ||
| tasks | ||
| README.rst | ||
Configure a host to be backed up
This role setups a host to use bup for backup to any
hosts in the 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 bup tool is installed and a cron job is setup to run
the backup periodically.
Note the backup-server role must run after this to
create the user correctly on the backup server. This role sets a tuple
bup_user with the username and public key; the
backup-server role uses this variable for each host in the
backup group to initalise users.
Role Variables
The username to connect to the backup server. If this is left undefined, it will be automatically set to
bup-$(hostname)