Changes

Jump to navigation Jump to search
844 bytes removed ,  12:54, 5 January 2021
m
fix: typo
Line 3: Line 3:  
* /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 [[Machine/housetree]]: daily filesystem backups for [[Machine/sunjammer]]
   
* /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 ==
* Bernie Innocenti <bernie AT sugarlabs DOT org>
  −
== Sysadmins ==
  −
  −
For non-emergency calls, preferably send email to the 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 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`.
 
The `wizbackup-driver` script runs daily on the backup servers from `/etc/cron.daily/wizbackup`.
Line 35: 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.
  −
== Restoring files from duplicity backups ==
  −
  −
To restore a backup try something like:
  −
  −
  duplicity restore -t 7D --file-to-restore <source/path/to/restore/from>  scp://sugarbackup@backup.sugarlabs.org/backup/<machine.sugarlabs.org>  </destination/path/to/restore/to>
  −
  −
* Replace <> with your values
  −
  −
  −
Example:
  −
  −
  duplicity restore -t 7D --file-to-restore var/lib/mysql/wordpress  scp://sugarbackup@backup.sugarlabs.org/backup/sunjammer.sugarlabs.org  /home/bernie/restore/wordpress
  −
  −
== See Also ==
  −
  −
* There are instructions on how to set up a backup here: [[Infrastructure_Team/Template_virtual_machine_lucid]]
      
[[Category:Service|zzz]]
 
[[Category:Service|zzz]]
79

edits

Navigation menu