Lewis Center for Neuroimaging
Effective Date: March 1, 2009
The Center provides a means whereby researchers may collect data during the course of
MRI experimentation. We maintain a number of systems based on RAID arrays and UPS
power backup to assure the integrity and availability of this data for a reasonable period
of time. In addition, we perform tape backups with offsite storage to guard against
catastrophic events such as fire or flood. This document outlines the details of our tape
Our backup system consists of a tape library supporting 2 Gbps data transfers controlled
by backup software that is likely to have good longevity. This software runs on the file
server for maximum performance. Where applicable, backups on media that become
obsolete over the course of time will be brought forward onto media that is likely to not
become obsolete in the near future. Other media offered to Center users include optical
disc (CD and DVD).
Generally speaking, only server machines are subject to backup. The Center has server-
based home directories, so there is no need to back up a typical workstation or compute
node. Backups are maintained on the following machines:
Bordeaux Main file server
Ragya Master DICOM repository
Mansfield Database server
Additions to this list may be evaluated on a case-by-case basis.
File systems backed up necessarily depend upon the machine on which they reside.
Current file systems selected for backup include:
Machine File system(s) Notes
Bordeaux /raid/data0/vxfsvol Includes public and staff
directories and home
directories for all user
Ragya I:\eFilm Medical eFilm DICOM image
Mansfield /usr/local/var/mysql-data Databases for web calendar
Onsite backup and recovery is provided through level 0, level 1 and level 9 backups, with
an expiration of two months for each backup. Level 0 is a full backup of all files and
directories for a given machine. Level 1 is a cumulative incremental backup, backing up
all files changed since the last level 0 backup. Level 9 is an incremental backup, backing
up all files changed since the last backup of any kind. The combination of these three
types provides the ability to restore to within 24 hours of a given point in time within the
Full archive backups, which are “snapshots” of a given file system at the time of the
backup, are also created. The purpose of these backups is to provide long-term recovery
and recovery in the event of loss of the onsite storage facilities. These archive backups
are moved offsite to a location in downtown Eugene. Expiration of full archive backups
is five quarters (15 months), which allows recovery to within three months of a given
point in time within the previous year.
Permanent archive backups are identical to full archive backups with the exception that
they are retained forever. Permanent archive backups are run in addition to full archive
backups when the data backed up must be retained forever. These backups are also
moved to the offsite storage vault.
Schedule & Retention
For the machines listed above, level 0 backups are run every month, level 1 backups are
run weekly, and level 9 backups are run daily. Full archives are created for Bordeaux at
the beginning of each calendar quarter. Permanent archives are created for ragya at the
beginning of each calendar quarter. A summary of the backup schedule is shown below.
Machine Level 0 Level 1 Level 9 Full Archive Perm. Archive
Bordeaux 2nd Friday Thursday Daily 1st Friday n/a
Ragya 2nd Wednesday Tuesday Daily n/a 1st Wednesday
Mansfield 2nd Tuesday Monday Daily n/a n/a
Additional schedules cover the needs of the Center to maintain permanent archives of
certain directories and files. These schedules are documented separately, and the backup
software may be consulted for the current set of such schedules.
Permanent archives existing as of the effective date of this policy will be retained through
2010. After that time, all permanent archives created prior to the effective date of this
policy will be destroyed. It is hoped that this sunset period will allow any researchers
ample opportunity to request recovery of any needed data. Exceptions to this effect
include any data falling into the category of Internal Resources, and raw DICOM data.