Time to go dust this game off on the Wii...
And a point about JBOD being useful for Exchange. In most Exchange environments I have worked with, replication happens at the appication layer, with huge portions of the data store being replicated amongst members of the Exchange Cluster, each with their own copy of the data. While expensive RAID/physical redundancy is a good idea, it is not critical as exact copies of the data store are available elsewhere in the cluster, and mailboxes can be failed over to those members.
And for the people that want a full RDBMS or SQL Server under the hood of Exchange - this is primarily a performance concern. Exchange access to data stores has such a unique profile that ca be modeled to show specific performance profiles that would benefit from a customized data access layer, overall Exchange performance would be hampered by the inclusion of an RDBMS that was designed to respond to a multitude of performance profiles. When you have the luxury of understanding how your application accesses data, it is best to choose (or develop) the data storage subsystem that will reap you the best performance. Here is where I believe Microsoft has the right approach.
I am the Command Line Interface Terrorism Master!!!
And don't forget to select "Enterprise Edition" when doing your Oracle install. Standard has a 2-node limit.
Isn't the Japanese space elevator supposed to fix this problem?
Unless the asteroid in question is small enough that it falls into the "OMFG HOW DID WE MISS THAT?!?! WE'RE DOOMED!!!" category. I can have a small asteroid knocking on our doorstep (a few hundred thousand kilometers, astronomically speaking) and still not be able to see it with the vast majority of instrumentation in our arsenal today.
Obviously to document anything related to Cost of Living Adjustments? Important in today's economy, no?
Or are you aware of a different type of cola?
I think you are missing the importance of a disaster recovery plan, with backups, for any mission critical hardware, regardless of vendor. Why didn't Mag have any sort of backup plan that was tested? Clustered hardware does not equal a backup plan - thanks for trying there.
Was there in fact a schedule of backups of the operational system? This seems like a rubber band and duct tape operation to me.
I believe that it all depends on whether or not you are using whole cats.