Skip to content
jdimatteo edited this page Oct 16, 2013 · 61 revisions

Gmail

Jenkins

  • http://tod.dfci.harvard.edu/jenkins
    • install documented at misc-2
  • tip: use for remote system admin, e.g.
  • only the bradneradmin user currently has permission to create/configure jobs
  • the jenkins user has sudo permission to run some backup scripts in /root/backup-scripts/
    • the jenkins user should still be safe to use for other jobs, and it would be fine to allow any authenticated user access to configure/create jenkins jobs
      • configuration is carefully setup to NOT allow the jenkins user to run arbitrary backup commands (which would allow a user to backup files they don't have access to to arbitrary locations, or restore files they wouldn't normally have access to)
  • dfbradnerlab@gmail.com email used for sending messages

Backups

TOD Path Backup Path
/ark /crusader/backup/rdiff-backup/ark/
/raider /crusader/backup/rdiff-backup/raider
/mnt/d0-0/share/bradnerlab/ /crusader/backup/rdiff-backup/mnt/d0-0/share/bradnerlab/
/ifs/labs/bradner/ /crusader/backup/rdiff-backup/ifs/labs/bradner/
/ --exclude /proc --exclude /sys --exclude /tmp --exclude /media --exclude /ark --exclude /raider --exclude /mnt --exclude /ifs --exclude /crusader /crusader/backup/rdiff-backup/root_directory/
root@tod:~# apt-get install automysqlbackup
root@tod:~# cp /etc/default/automysqlbackup gunk/
root@tod:~# vim /etc/default/automysqlbackup
root@tod:~# diff gunk/automysqlbackup /etc/default/automysqlbackup 
31c31
< BACKUPDIR="/var/lib/automysqlbackup"
---
> BACKUPDIR="/crusader/backup/automysqlbackup"
39c39
< MAILCONTENT="quiet"
---
> MAILCONTENT="stdout"
root@tod:~# mv /etc/cron.daily/automysqlbackup gunk/
  • the actual commands to do the backups are in scripts in /root/backup-scripts, which the Jenkins user has sudo access to
  • note that Charles suggested that /crusader has good physical security, so this should be secure enough without encryption
  • Common Errors
    • "UpdateError" - this is a recoverable error, effecting just a single file that failed to be backed up because it was being modified during the backup. See http://rdiff-backup.stanford.edu/error_policy.html for more info. Usually no action needs to be taken, since all other files were backed up correctly and this single file will probably be backed up successfully during the next backup.
  • TODO: schedule restore drills to verify integrity of backups

Misc.

  • some apt-get installed software (this isn't intended to be a complete list) ** automysqlbackup

Clone this wiki locally