1,784
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + − * /backup on sunjammer.sugarlabs.org: daily database dumps (ldap, mysql and pgsql) for [[Machine/sunjammer]] Line 11:
Line 10: − + Line 23:
Line 22: − − == 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.
no edit summary
== Locations ==
== Locations ==
* /backup on [[Machine/justice]]: daily filesystem backups for [[Machine/freedom]]
* /backup on [[Machine/papert]]: daily filesystem backups for [[Machine/bender]] and [[Machine/sunjammer]]
* /backup on [[Machine/freedom]]: daily filesystem backups for [[Machine/justice]]
* /backup on [[Machine/bender]]: daily filesystem backups for all VMs hosted on [[Machine/papert]]
== Administrative contact ==
== Administrative contact ==
* [https://codewiz.org/gitweb/wizbackup.git Source code]
* [https://codewiz.org/gitweb/wizbackup.git Source code]
* [https://codewiz.org/gitweb/wizbackup.git/blob/HEAD:/INSTALL Installation instructions]
* [https://codewiz.org/gitweb/wizbackup.git/blob/HEAD:/README.md README]
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).
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).
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`).
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`).
[[Category:Service|zzz]]
[[Category:Service|zzz]]