Difference between revisions of "Backups"
| Line 8: | Line 8: | ||
# Put new drive in. (there are 4 screws holding the drive in place). | # Put new drive in. (there are 4 screws holding the drive in place). | ||
# Slide it back in. Take note which Linux drive it registers as: /dev/sdb or /dev/sdc or /dev/sdd or /dev/sde <br> NOTE: The order does NOT correspond with the slots, and this order can change after a reboot! | # Slide it back in. Take note which Linux drive it registers as: /dev/sdb or /dev/sdc or /dev/sdd or /dev/sde <br> NOTE: The order does NOT correspond with the slots, and this order can change after a reboot! | ||
| − | # Run /usr/local/bin/format_archive_disk.pl <disk no> <device> <br> I.E: /usr/local/bin/format_archive_disk.p 29 /dev/sde | + | # Run /usr/local/bin/format_archive_disk.pl <disk no> <device> <br> I.E: /usr/local/bin/format_archive_disk.p 29 /dev/sde[http://www.mikerubel.org/computers/rsync_snapshots/] |
# Check that the drive is available: ls /mnt/npg-daily/29 | # Check that the drive is available: ls /mnt/npg-daily/29 | ||
| Line 17: | Line 17: | ||
Newer backups do something involving hard-linking files that haven't changed between backup sessions. Seems like a good idea, but we need to learn exactly how it works. | Newer backups do something involving hard-linking files that haven't changed between backup sessions. Seems like a good idea, but we need to learn exactly how it works. | ||
For old backups in the new format, consolidation works by putting all the data from each backup session into one place, overwriting with the newest data. Nobody's going to look for a specific version of a file they had in 2004 that only existed for three days, so this method is relatively safe, in terms of data retention. | For old backups in the new format, consolidation works by putting all the data from each backup session into one place, overwriting with the newest data. Nobody's going to look for a specific version of a file they had in 2004 that only existed for three days, so this method is relatively safe, in terms of data retention. | ||
| + | |||
| + | Here [http://www.mikerubel.org/computers/rsync_snapshots/] is a nice little guide on incremental, hardlinked backups via rsync. He sets up some nice little tricks with NFS mounts so that users can access their stuff read-only for any backup that's actually stored. We should do this. | ||
Revision as of 18:12, 19 June 2007
NPG backups runs from the dedicated backup server: Lentil Lentil has 4 hot-swappable drive bays, which can contain SATA drives.
To put in a new (fresh drive):
- Locate the oldest disk.
- Make sure it is not mounted.
- Open the appropriate drive door and slide out drive.
- Put new drive in. (there are 4 screws holding the drive in place).
- Slide it back in. Take note which Linux drive it registers as: /dev/sdb or /dev/sdc or /dev/sdd or /dev/sde
NOTE: The order does NOT correspond with the slots, and this order can change after a reboot! - Run /usr/local/bin/format_archive_disk.pl <disk no> <device>
I.E: /usr/local/bin/format_archive_disk.p 29 /dev/sde[1] - Check that the drive is available: ls /mnt/npg-daily/29
The really old amanda-style backups are tar'ed, gzip'ed, and have weird header info. Looking at the head of them gives instructions for extraction.
A script was written to extract and consolidate these backups. Shrinks hundreds of gigs down to tens of gigs, and zipping that shrinks it further. Very handy for OLD files we're not going to look at ever again.
Newer backups do something involving hard-linking files that haven't changed between backup sessions. Seems like a good idea, but we need to learn exactly how it works. For old backups in the new format, consolidation works by putting all the data from each backup session into one place, overwriting with the newest data. Nobody's going to look for a specific version of a file they had in 2004 that only existed for three days, so this method is relatively safe, in terms of data retention.
Here [2] is a nice little guide on incremental, hardlinked backups via rsync. He sets up some nice little tricks with NFS mounts so that users can access their stuff read-only for any backup that's actually stored. We should do this.
