We have medium-high availability. Our db servers run fibre channel over to our EVA, which is a single-point of failure. (I know it's got redundant this and that.) If a box goes belly up, we created a script that transfers all of the storage from our production box to a test box. (All db servers are identical.) Total down time should be <5 minutes. That includes detecting the problem.
Our investment accounting system runs on a cluster, serviced by the same EVA. The amusing thing is, if a cluster node goes down and the db needs to migrate to the new node, SQL Server will stop for a couple of seconds (as expected), the problem is... The IA system is so well written, that if SQL server goes down, it'll puke and die, but not before corrupting the databases that support it. I could go into detail as to why, but let's just say they (the vendor) do not believe in such trivial things as transactional integrity, indexing schemes, data validation, stored procedures, system views (why bother when you can update the system tables directly?)... You get the idea.
I like the idea of our current environment, along with the addition of log shipping down to our DR site.
We're on a 15 minute lag, so for us it's not bad. After all, we're not Wal-mart, or Amazon...
(Steve, nice new pic... Shamed me into changing mine.)
Honor Super Omnia-