Not logged in
Talk
Contributions
Create account
Log in
Navigation
Main page
About
People
Publications
Teaching
Resources
Research Blog
Wiki Functions
Recent changes
Help
Licensing
Project page
Discussion
Edit
View history
Editing
CommunityData:Backups (nada)
From CommunityData
Jump to:
navigation
,
search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
'''nada.com.washington.edu''' (our main Internet-connected research server at the University of Washington) has about 14TB of available disk space. The disks are in a [https://enw.wikipedia.org/wiki/RAID5 RAID5 configuration]. This means that if there's hardware failure on one drive, we won't lose data. If there is hardware failure on more than one drive through bad luck, some sort of physical accident that destroys the machine (e.g., fire), or if someone accidentally deletes files they need, we'd be out of luck. As a result, we have backups. Although we would love to backup thing everything, backing up all 14TB would cost about $140/month! As a result, we are trying be smart about what/how we back things up. This page discusses the current backup setup and strategy. == Backups on Nada == Nada backups are full filesystem-wide backups using [http://duplicity.nongnu.org/ Duplicity]. The backups are incremental backups done weekly using [http://www.nongnu.org/rdiff-backup/ rdiff backup] (think [https://rsync.samba.org/ rsync]), are encrypted using a GPG key under Mako's control, and are stored in [https://cloud.google.com/storage/docs/nearline?hl=en Google Nearline storage] which costs about $0.01/GB. Backups run once at the beginning of each week. Everything is backed up except for the directories listed in <code>/root/duplicitity_exclude</code>. This page may not be up to date but the following files/directories are '''excluded''' at the time that this page was written: /mnt /media /mit /nonexistent /openafs_cache_fs /tmp /var/log /var/lib/mysql /var/lib/mongodb /var/lib/redis /var/lib/postgresql /var/spool /var/tmp /var/cache /lost+found /lolo /cdrom /floppy /proc /sys /root/.cache /root/nobackup /home/*/.cache /home/*/nobackup /home/awjordan == Backing up Databases == === MySQL Backups === Although <code>/var/lib/mysql</code> is excluded, some MySQL databases '''are backed up'' using a separate MySQL incremental backup script that calls [https://www.percona.com/software/mysql-database/percona-xtrabackup Percona XtraBackup]. These incremental MySQL backups are created once each week before the duplicity backup script is run. To add a new MySQL database to the backup list, you should edit the following files: /usr/local/sbin/mysql_backup_full /usr/local/sbin/mysql_backup_inc == Minimizing Backup Size == If you have large datasets that are unlikely to change or be replaced, store a copy of these data in the <code>/com/</code> directory in Hyak and keep the files in <code>/home/<YOUR NAME>/nobackup</code> and then symlink them from a more convenient location.
Summary:
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see
CommunityData:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Tools
What links here
Related changes
Special pages
Page information