 |
1776® Fault-Freedom™ II
Benefits Checklist
Estimate typical financial costs for each type of event listed below.
BENEFITS SHARED WITH TRADITIONAL CLUSTERING
- Protection against server failure - I assume you are concerned with server hardware failure and operating system crashes. How much do you figure it costs each time such a failure occurs, in terms of immediate lost business, wasted employee time, and loss of customer confidence?
- Software crash recovery - Is the system running a database system or some other critical program that could crash and bring the whole system down when it does? If so, what do you think that would cost each time it occcurs?
BENEFITS NOT AVAILABLE WITH TRADITIONAL CLUSTERING
- Protection against loss of "current data" - To what degree are you aware of the enormous cost of losing a day's worth of data transactions, if you had to restore your entire database from a day-old backup tape? How much do you think that would cost the company today?
- Protection against most typical site disasters ("localized disaster recovery") - How much are you concerned about typical site disasters, like fire, theft, vandalism, water damage, or lightning strikes, events that could destroy part of a building but would probably not destroy the entire site?
- Protection against storage subsystem failure - To what degree are you aware of the danger in using a traditional cluster, wherein the shared array is the single-point-of-failure?
OTHER IMPORTANT BENEFITS
- On-line system maintenance - How meaningful is it to be able to carry out system maintenance and upgrades while the system is in operation?
- On-line tape backup ("Snap-Shot") - Is the system running nearly 24 hours? If so, how useful would it be to run tape backups while the system is in operation?
- Major disaster recovery - To what degree are you concerned with major disaster scenarios such as large hurricanes, tornados, or earthquakes that could wipe out an entire site of neighborhood?
|
| |
|
