[223] in Athena_Backup_System
Integrating cleanly into requirements doc.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Thu Mar 28 19:07:51 1996
Date: Thu, 28 Mar 1996 19:07:42 -0500 (EST)
From: Bill Cattey <wdc@MIT.EDU>
To: athena-backup@MIT.EDU
The way we phrased the cleanly definition last week didn't quite fit
with the prose as it was stated in the requirements doc.
Subject to the approval of the assembled masses, I did the following:
I spun out mention of degraded operation into a separate subsection
called CRIPPLED MODE.
I tuned it to benefit from our recent discussions of crippled mode.
I recast the prose on cleanly and put it under either System or Database
requirements.
I added an explicit requirement (that we implied) that keeping Oracle in
"Archive Log" mode would provide adequate performance. (I said
"will provide performance comensurate with meeting the performance
requirements stated elsewhere in this document." which I felt was both
explicit and vague enough for all parties concerned.
Below are the context diffs so you can see what I did.
Is it OK?
-wdc
diff -c -r1.5 requirements
*** /tmp/,RCSt1011605 Thu Mar 28 19:06:26 1996
--- requirements Thu Mar 28 19:01:39 1996
***************
*** 76,87 ****
7) The system will provide a way to save and restore an external ascii
(human readable form) image of the data base.
! 8) The system shall be able to perform restores when the master is
! incapacitated. This feature shall be accessed by a simple client that
! can talk to the slave. It's permisible for the slave to be restarted
! to know to talk to the simple client. The correlation for the tape to
! volume information will be provided by the ASCII backup of the Master.
SYSTEM:
1) The system shall have an ascii command line interface
--- 76,93 ----
7) The system will provide a way to save and restore an external ascii
(human readable form) image of the data base.
! 8) In the event of a database disk failure, the Procedures documented
! Oracle Systems Administrator's guide will be followed for system
! recovery.
! NOTE: It is a configuration requirement that Oracle operate in
! "Archive Log" Mode for this recovery to restore up to the
! the last committed transaction, rather than the last full
! backup of the Oracle Database.
+ 9) The database will be so configured that operation in "Archive Log"
+ mode will provide performance comensurate with meeting the performance
+ requirements stated elsewhere in this document.
+
SYSTEM:
1) The system shall have an ascii command line interface
***************
*** 131,137 ****
13) Slave shall retry "important" calls indefinitely. These calls
are: job_done, validate_media, job_attention.
! 14) System must recover cleanly from a power failure.
DATA:
--- 137,168 ----
13) Slave shall retry "important" calls indefinitely. These calls
are: job_done, validate_media, job_attention.
! 14) In the event of a failure of the Master, or a reboot of the
! machine on which the Master resides, the database restarts
! only after intervention of a Database Administrator. The
! administrator needs to verify that the integrity checks are
! present and to fix any inconsistency flagged by Oracle.
!
! CRIPPLED MODE
!
! 1) The system shall be able to perform dumps and restores when the
! database is offline through the use of a Crippled Mode Master.
!
! 2) Crippled mode does not offer full functionality.
!
! 3) Crippled mode must provide the ability to dump and restore volumes
! and partitions with recording of what was done for explicit input
! to the database when it comes back online.
!
! 4) Crippled Mode will only be used as a short term EMERGENCY mode of
! operation.
!
! 5) It's permisible for the slave to be restarted to know
! to talk to the crippled mode master.
!
! 6) The correlation for the tape to volume information will be provided by
! the ASCII backup of the Master.
!
DATA:
