What we do — and don't do — to protect data stored on our systems.
All of our critical servers use RAID (Redundant Array of Inexpensive Disks) to improve reliability. This allows the loss of at least one hard disk without any data being lost. In many cases the disk can be replaced and the array rebuilt without the system ever being shut down.
All user data stored on our servers is backed up. Generally backups are run nightly, with the exception of monthly full backups, which can take up to three days to complete due to the volume of data involved.
Currently there are no off-site backups. Backups are stored on campus, although they are in a different building. This means a widespread disaster could destroy both the original data and the backup.
Because of the lack of off-site backups, you should retain your own copies of any data you cannot afford to lose. We highly recommend that you store these copies off campus, to minimize the chances of them being destroyed should a natural disaster affect the UW campus. Remember, we live in an area where severe and sudden geological hazards exist.
After the Northridge earthquake, some researchers at California State University-Northridge lost their life's work when buildings burned down or were contaminated by hazardous materials. Don't let this happen to you!
If you need assistance in determining the best way to package up your data for downloading or transfer to other media, email linghelp@u.
If you accidentally delete or overwrite an important file, you can ask to have it retrieved from backup. Note that backups are mainly meant as a way of recovering a failed server, and are not an archival system or a substitute for version control! They may expire in as little as two weeks, depending on disk space needs.
Requesting file restoration from the backup server
to arrange to have a file retrieved from backup. Entire directory trees can be restored if necessary. Please provide enough information to identify the correct version of the file, if it has been overwritten; for example, the approximate modification date and/or size. Keep in mind that any changes since the most recent backup cannot be recovered.
Topic revision: r4 - 2015-09-18 - 20:17:52 - brodbd