Overview
The departmental backup system is designed to regularly back up data (not software and operating systems) to a disk & tape system hosted over the road in the Cambridge Systems Biology Centre. For the purposes of these pages "Backup" (as opposed to "archival") is copying data from rapid access systems onto cheaper storage in order to recover from accidents or system failures. Copies are only kept for a limited period of time. Systems to be backed up must be on the wired network and be turned on during the backup period.
Servers are backed up in the evening:
- On Tuesdays, Wednesdays and Thursdays the changes since the previous backup are saved to off site disk. This information is kept for a month, and can be retrieved within 1 working day.
- On the second and fourth Fridays all changes since the last full backup are saved to off site disk. This information is kept for 3 months, but will be moved onto tape if disk space becomes low. It can take a day or two to retrieve.
- Every three months, on the first Friday, a complete copy of the data is stored to off site tape. This information is kept for a year. The specific month varies by server in order to spread the load, see the table below. Retrieval of this data is likely to take many days.
Desktops are backed up around lunchtime:
- On Wednesdays, Thursdays and Fridays the changes since the previous backup are saved to off site disk. This information is kept for a month.
- On the second and fourth Tuesdays of a month all changes since the last full backup are saved to off site disk. This information is kept for 3 months, but will be moved onto tape if disk space becomes low.
- On the first Tuesday of January, April, July and October a complete copy of the data is stored to off site tape. This information is kept for a year.
If more than 100 gigabytes is to be backed up the system must be on a gigabit (1000 megabit/second) rather than a 100 megabit/second network connection, otherwise they'll block the tape system for more than 3 hours.
Usage
List of backed up systems, and when their full backup is taken:
| System Name | Connection Speed (Megabits/second) |
Full Backup Schedule (Normally every 3 months) |
Total Size of Backups (As of 13-Jun-2012) |
|---|---|---|---|
| admin-linux1 | 1000 | jan/apr/jul/oct | 8GB |
| amaserv | has own tape drive | feb | 3998GB |
| central | 1000 | feb/may/aug/nov | 15311GB |
| db | 1000 | feb/may/aug/nov | 554GB |
| dcrowtherpc | 100 | feb/may/aug/nov | 3GB |
| dmgarchive | 1000 | mar/jun/sep/dec | 17201GB |
| flysoxserver | 100 | feb/may/aug/nov | 1366GB |
| heidi | 1000 | mar/jun/sep/dec | 354GB |
| keyserver | 1000 | feb/may/aug/nov | 209GB |
| kyala | 1000 | mar/jun/sep/dec | 0GB |
| larch | 2000 | jan/apr/jul/oct | 37110GB |
| libpc4 | 100 | ad hoc | 156GB |
| 1000 | jan/apr/jul/aug | 93GB | |
| malibu | 1000 | mar/jun/sep/dec | 0GB |
| multivac | 1000 | mar/jun/sep/dec | 0GB |
| newwebb | 100 | ad hoc | 162GB |
| officepc4 | 100 | ad hoc | 46GB |
| officepc5 | 100 | ad hoc | 50GB |
| salijeax | 100 | ad hoc | 1056GB |
| vmd-qnap | 1000 | jan/apr/jul/oct | 9013GB |
| xena | 100 | mar/jun/sep/dec | 505GB |
-->
I get a report on every backup that occurs and check a random file every month to ensure things are ticking over OK.
Do you need it?
- If you're storing data on larch then your data is already backed up except for contents of folders containing a ".nobackup" file or folder.
- If you are using a PC with the "DEPT" login, data in your "Documents" and "Desktop" folders is on the server "Larch" so is already backed up (See #1 above.) If you are storing elsewhere then it will not be.
- Some lab servers are backed up too. Ask in your group. If no one knows then you have a problem in your lab.
Compared to using a hard disk
- Data offsite can only be written to by the backup software. If you get a virus that attempts to destroy or encrypt your data it can't directly attack backups through this system
- If you are backing up to a USB disk or NAS viruses can quite quickly delete and overwrite things.
- It is slower and more complicated to recover data from the backup system.
- Doing both is not harmful
- If you manage your own backups you need to check they are working.