[250] in Athena_Backup_System
Revised Crippled Mode requirements
daemon@ATHENA.MIT.EDU (wdc@MIT.EDU)
Fri May 31 18:21:08 1996
From: wdc@MIT.EDU
To: athena-backup@MIT.EDU
Cc: wdc@MIT.EDU, jis@MIT.EDU
Date: Fri, 31 May 1996 18:20:56 EDT
As per our discussion at the most recent ABS meeting, I have
revised the crippled mode requirements.
Would people please comment on them before I declare them dogma.
Jeff: Is this good enough, now that we here in E40 have ramped up
to higher levels of understanding and responsibility in the care
and feeding of Oracle?
-wdc
CRIPPLED MODE
1) The system shall be able to perform restores of individual volumes
and file server partitions when the database or Master is offline
through the use of a Crippled Mode user interface client.
2) Crippled mode does not offer full functionality. Restore only is
acceptable.
3) Crippled Mode will only be used as a short term EMERGENCY mode of
operation.
4) It's permisible for the slave to be restarted to know to talk
to the Crippled Mode user interface client.
5) The correlation for the tape to volume information and tape to
partition information will be provided by an ASCII report that is
produced as part of periodic maintenance procedures.
6) A Crippled Mode interface client need only handle a single media
slave.
7) It is acceptable that Crippled Mode limit the number of slaves
which can run simultaneously on a single host.
8) It is acceptable that Crippled Mode limit the number of slaves which
can be concurrently active throughout the ABS domain.
9) Crippled Mode should provide a means to funnel all error messages
and event notifications from all components through a single channel.
10) Rather than resorting to the complexity of supporting scheduled dumps,
and offline database update in Crippled Mode, rigorous database backup
and disaster recovery plans will be documented, followed, and
periodically tested in keeping with proper operational procedures.
