1,764
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − * /backup on [[Machine/housetree]]: daily filesystem backups for [[Machine/sunjammer]] − * Bernie Innocenti <bernie AT sugarlabs DOT org> − == Sysadmins == − − For non-emergency calls, preferably send email to the administrative contact. − − + − +
no edit summary
* /backup on [[Machine/justice]]: daily filesystem backups for [[Machine/freedom]]
* /backup on [[Machine/justice]]: daily filesystem backups for [[Machine/freedom]]
* /backup on [[Machine/freedom]]: daily filesystem backups for [[Machine/justice]]
* /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]]
* [[User:Bernie|Bernie Innocenti]]
== wizbackup ==
== wizbackup ==
* [http://codewiz.org/gitweb/wizbackup.git Source code]
* [https://codewiz.org/gitweb/wizbackup.git Source code]
* [http://codewiz.org/gitweb/wizbackup.git/blob/HEAD:/INSTALL Installation instructions]
* [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 snapashots 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 snapashots 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).