Difference between revisions of "Service/backup"

From Sugar Labs
Jump to navigation Jump to search
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Locations ==
 
== Locations ==
  
* /backup on treehouse.sugarlabs.org (for sunjammer)
+
* /backup on [[Machine/justice]]: daily filesystem backups for [[Machine/freedom]]
* backup.sugarlabs.org (all the other systems)
+
* /backup on [[Machine/freedom]]: daily filesystem backups for [[Machine/justice]]
* /backup on sunjammer.sugarlabs.org (of sunjammers services: git, mysql and pgsql)
+
* /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.sugarlabs.org ==
 
 
 
[Machine/owl owl.laptop.org:/home/sugarbackup/]
 
  
 
== Administrative contact ==
 
== Administrative contact ==
 
+
* Bernie Innocenti <bernie AT sugarlabs DOT org>
bernie AT sugarlabs DOT org
 
 
 
 
 
 
== Sysadmins ==
 
== Sysadmins ==
  
Line 20: Line 14:
 
* [[User:Bernie|Bernie Innocenti]]
 
* [[User:Bernie|Bernie Innocenti]]
  
 +
== wizbackup ==
  
== Restore Backups ==
+
* [http://codewiz.org/gitweb/wizbackup.git Source code]
 
+
* [http://codewiz.org/gitweb/wizbackup.git/blob/HEAD:/INSTALL Installation instructions]
To restore a backup try something like:
 
  
  duplicity restore -t 7D --restore-time <yyyy/mm/dd --file-to-restore <source/path/to/restore/from>  scp://sugarbackup@backup.sugarlabs.org/backup/<machine.sugarlabs.org>  </destination/path/to/restore/to>
+
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).
  
* Replace <> with your values
+
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:
  
Example:
+
  wizbackup <hostname>:/ <local-backup-dir> --exclude-file /backup/EXCLUDE/ALWAYS --exclude-file /backup/EXCLUDE/<hostname>
  
  duplicity restore -t 7D --restore-time 2000/01/01 --file-to-restore var/lib/mysql/wordpress  scp://sugarbackup@backup.sugarlabs.org/backup/sunjammer.sugarlabs.org  /home/bernie/restore/wordpress
+
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 ==
  
the --restore-time is a workaround for a bug in duplicity when restoring backups in the past
+
[[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.
  
 +
== Restoring files from duplicity backups (OBSOLETE) ==
  
== Notes ==
+
'''We no longer use Duplicity.'''
  
This is the main backup server for all [[Machine|Sugarlabs Machines]]
+
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>
  
== Upgrade notes ==
 
  
 +
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: http://wiki.sugarlabs.org/go/Infrastructure_Team/Template_virtual_machine_lucid
 
  
 
[[Category:Service|zzz]]
 
[[Category:Service|zzz]]

Revision as of 19:50, 5 April 2015

Locations

Administrative contact

  • Bernie Innocenti <bernie AT sugarlabs DOT org>

Sysadmins

For non-emergency calls, preferably send email to the 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 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).

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.

Restoring files from duplicity backups (OBSOLETE)

We no longer use Duplicity.

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>


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