Backups

From Peyton Hall Documentation

Jump to: navigation, search

Data stored on hard drives has become very precious to many. In some cases, the ones and zeros written to disk can mean weeks, months or years worth of work to their author, and in other cases (such as data from a telescope run) they can never be recovered. For this reason, we not only have some redundant systems in place, but also some backup systems to try to make sure important data is never lost.


Contents

What is backed up?

Unfortunately, backing up data (or keeping it on highly reliable media) can be expensive. Because of that, we cannot afford to backup everything. However, everything that is stored in /u is backed up, as well as kept on a very reliable NFS server (made by Network Appliance). We also backup everything from the email server.

We do not backup scratch disks! The very nature of a scratch disk is that it's used for temporary storage of data and intermediate files; perhaps a local copy of data you have on CD elsewhere, or some outputs for in-between states of a data pipeline. Read Scratch disks for more information.

On-site backups

Snapshots

The central file server (which stores your home directory in /u) has a feature available called snapshotting. Every two hours a "snapshot" of the current state of your files is taken and frozen. This is useful if you accidentally delete a file or discover that a file is corrupt, as it means you can "roll back the clock" so to speak and recover an earlier version of your file.

Snapshots for your directory are located in the ~/.snapshot directory (you won't see it in a directory list, but it *is* there if you 'cd' to it). Under that directory you'll see other directories with names like "hourly.0" or "nightly.0". The higher the number, the older the snapshot is. hourly.0 was taken at the last even hour, hourly.1 was from two hours before that, and so on. The nightly snapshots are taken at midnight, so nightly.0 is the state of your files at midnight this morning, and nightly.1 is midnight the day before.


How to recover via snapshots

To recover a snapshot, just copy the file from the snapshot directory to anywhere in your home directory. Note that you won't be able to delete, rename, or otherwise modify anything under .snapshot as it's read only.

If you need to recover a file from your home directory older than the available snapshots, please contact us as soon as possible so we can recover it from the nightly backups which are performed on the central file server.


Off-site backups

Every night, starting around 0130, the home directory server is backed up to OIT's TSM servers. This doesn't always succeed - sometimes their servers are overloaded and backups don't complete, but that's why we have the snapshot feature turned on. Files that are backed up via TSM are kept for 90 days from the date of their deletion, and the last four revisions of a file are kept as well. This means that if you discover a file is corrupted, and it's been changed three or less times, we can probably recover a version of the file before it was corrupted.

NOTE:

To give the best chance that we can recover a file for you, you MUST contact us as soon as you realize you need a file recovered! The longer you wait, the less chance there is that we can get the file back.


Recovering files via TSM

Due to the way TSM operates, you cannot restore your own files that were on the home directory server. We will have to run the restore for you. Please contact us as soon as you realize you need a file restored so we have a better chance of recovering it for you.


Personal backups

If you have a laptop and want to back it up (you should, unless you wouldn't care at all if all the data disappeared suddenly - and since laptops travel around, they're more prone to breakage and drive failure than most desktops), there's a couple options.

Personal TSM backups

Pros:

  • Backups are handled by the software automatically (with few exceptions)
  • Off-site storage decreases chance of laptop and backup both falling victim to a disaster
  • You don't have to manage the backup storage, TSM handles it for you

Cons:

  • Your laptop must be plugged in to the network to backup (wireless will work in a pinch, but be painfully slow)
  • If you need to restore a file, you must be plugged in to the campus network
  • If you write data while on a trip, and aren't back in the building before a failure, you won't have a backup

See the TSM link above for information on registering your laptop for the TSM backup services.


External storage device

Another solution for backing up a laptop is an external storage device, such as a USB or Firewire hard drive enclosure.

Pros:

  • Your laptop can be backed up any time you like, as long as you have the drive with you
  • No recurring fee for backups, and many enclosures can have their drives replaced for future expansion
  • Restores can happen anytime and anywhere, as long as your backup drive is nearby

Cons:

  • You are responsible for storing the backups
  • If your backup drive and laptop are both in the office during a disaster, you could lose both


See also

Personal tools