[150] in Athena_Backup_System
Review of Requirements
daemon@ATHENA.MIT.EDU (Bill Cattey)
Mon Dec 18 14:50:35 1995
Date: Mon, 18 Dec 1995 14:50:10 -0500 (EST)
From: Bill Cattey <wdc@MIT.EDU>
To: vrt@MIT.EDU, athena-backup@MIT.EDU
I'll take a stab on #1, the crippled configuration req:
The athena backup system will backup and restore at the granularity of:
An entire disk partition full of volumes.
A single volume.
A single file. <- Did we ever decide to do this or to NOT do this?
The backup and restore operations should be possible even in the event
of a failure of the database supporting the backup system Master process
through the implementation of a manual mode.
It should be possible to determine what volumes are on a given tape or
tapeset even in the absence of the Master and its database through a
tape scan utility.
It should be possible to re-create the database through:
native mode binary backups of the database.
human-comprehensible, ASCII backups of the database.
the output of the tape scan utility together with other outside human
readable backups of such tables as the backup schedule, and the status
logs made by the tape slaves.
The system should initially perform to be able to back up the current
file universe of 200GB such that the entire universe could be backed up
in one week's cycle time.
Through the addition of tape slaves, the system should scale up to being
able to back up an entire universe of 1000GB or more in one week's cycle
time.
-wdc
