Difference between revisions of "Service/backup"
m (fix: typo) |
|||
| (11 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Locations == | == Locations == | ||
| − | * /backup on [[Machine/ | + | * /backup on [[Machine/justice]]: daily filesystem backups for [[Machine/freedom]] |
| − | * /backup on [[Machine/ | + | * /backup on [[Machine/freedom]]: daily filesystem backups for [[Machine/justice]] |
* /backup on sunjammer.sugarlabs.org: daily database dumps (ldap, mysql and pgsql) for [[Machine/sunjammer]] | * /backup on sunjammer.sugarlabs.org: daily database dumps (ldap, mysql and pgsql) for [[Machine/sunjammer]] | ||
| − | |||
== Administrative contact == | == Administrative contact == | ||
| + | * [[User:Bernie|Bernie Innocenti]] | ||
| − | + | == wizbackup == | |
| − | + | * [https://codewiz.org/gitweb/wizbackup.git Source code] | |
| + | * [https://codewiz.org/gitweb/wizbackup.git/blob/HEAD:/INSTALL Installation instructions] | ||
| − | + | This is the main backup script for all [[Machine|Sugar Labs Machines]]. It's a minimalist script based on rsync and keeps a history of N days using hard-links. While it's very very simple, wizbackup gets the job done and has the added benefit of not requiring any tools to read or restore a backup. The advantage over similar backup solution is that backups are just plain filesystem snapshots of the source machines; the main disadvantage is poor performance with large files which change often, such as logs or databases (my solution is to exclude these and backup the data using ad-hoc methods, such as SQL dumps). | |
| − | + | The `wizbackup-driver` script runs daily on the backup servers from `/etc/cron.daily/wizbackup`. | |
| − | + | It reads a list of hostnames to backup from `/backup/HOSTS/<machine-group-name>` and an optional list of files exclusions from `/backup/EXCLUDES`, in the same format taken by the `--exclude` flag of rsync. | |
| − | + | For each machine in the list, `wizbackup-driver` invokes `wizbackup` with this command-line: | |
| − | + | wizbackup <hostname>:/ <local-backup-dir> --exclude-file /backup/EXCLUDE/ALWAYS --exclude-file /backup/EXCLUDE/<hostname> | |
| − | + | Wizbackup uses rsync and ssh to connect to the remote machine. Hence, the backup server must be authorized to connect as root to all backup hosts (e.g.: by storing the identity in `/root/.ssh/authorized_keys`). Wizbackup reads the ssh private key from `/etc/wizbackup/ssh_id`). | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Sunjammer == | == Sunjammer == | ||
| Line 34: | Line 29: | ||
The MySQL, PostgreSQL and LDAP databases are being backed up daily on backup.sugarlabs.org, encrypted with gpg. TODO: at the moment, we don't have a script to cleanup old backups. | The MySQL, PostgreSQL and LDAP databases are being backed up daily on backup.sugarlabs.org, encrypted with gpg. TODO: at the moment, we don't have a script to cleanup old backups. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Service|zzz]] | [[Category:Service|zzz]] | ||
Latest revision as of 12:54, 5 January 2021
Locations
- /backup on Machine/justice: daily filesystem backups for Machine/freedom
- /backup on Machine/freedom: daily filesystem backups for Machine/justice
- /backup on sunjammer.sugarlabs.org: daily database dumps (ldap, mysql and pgsql) for Machine/sunjammer
Administrative contact
wizbackup
This is the main backup script for all Sugar Labs Machines. It's a minimalist script based on rsync and keeps a history of N days using hard-links. While it's very very simple, wizbackup gets the job done and has the added benefit of not requiring any tools to read or restore a backup. The advantage over similar backup solution is that backups are just plain filesystem snapshots of the source machines; the main disadvantage is poor performance with large files which change often, such as logs or databases (my solution is to exclude these and backup the data using ad-hoc methods, such as SQL dumps).
The `wizbackup-driver` script runs daily on the backup servers from `/etc/cron.daily/wizbackup`. It reads a list of hostnames to backup from `/backup/HOSTS/<machine-group-name>` and an optional list of files exclusions from `/backup/EXCLUDES`, in the same format taken by the `--exclude` flag of rsync.
For each machine in the list, `wizbackup-driver` invokes `wizbackup` with this command-line:
wizbackup <hostname>:/ <local-backup-dir> --exclude-file /backup/EXCLUDE/ALWAYS --exclude-file /backup/EXCLUDE/<hostname>
Wizbackup uses rsync and ssh to connect to the remote machine. Hence, the backup server must be authorized to connect as root to all backup hosts (e.g.: by storing the identity in `/root/.ssh/authorized_keys`). Wizbackup reads the ssh private key from `/etc/wizbackup/ssh_id`).
Sunjammer
Machine/sunjammer's filesystem is being backed up on Machine/treehouse using rsync + 7 days of history with hard links.
The MySQL, PostgreSQL and LDAP databases are being backed up daily on backup.sugarlabs.org, encrypted with gpg. TODO: at the moment, we don't have a script to cleanup old backups.