being clustered certainly makes it more 'interesting'

the work I have done in this area was not on a cluster unfortunately. I can foresee problems with IP addresses, other than that (BIG caveat)the advice should basically hold true. Analysis services should be fine if the olap\data directories are replicated.

Two things

- expecting it to just work in SQL because 'thats how we do it in Oracle' is wishful thinking by people who should know better. The architectures are too different and its a mistake to try and force them to work the same. Main issues are SQL's close linking to the server name and the fact the install always puts some part of the installation to the C drive, no matter where you point the installation at.

- the apps people are shifting a lot of responsibility to you by expecting the same server name. with proper change and control procedures servername changes should be possible and connection strings should not have server names harcoded in them, DNS could be used for instance.

Try it in your POC, but allow time to also investigate only replicating drives with the user database and analysis services data on, the process of failing over during a DR will be a lot less complicated and quicker that way.

another option that would work very well for you is to upgrade OS to windows 2008 and use a geo-cluster. This is a setup where each node is connected to a different physical SAN and you replicate with SRDF in your instance between the SANS.