We are currently building a secondary facility to act as our Hot Site for disaster recovery. The secondary site is directly connected via fiber so speed and network connectivity is not an issue. We currently have several 2 node 2008 Server failover clusters. SQL and File Servers and Exchange. We would like to physically move 1 node to facility B and keep 1 node at the primary data center in facility A. We have A SAN that houses data at Facility A and we do Async replication to another SAN at facility B. The data will likely only be 4 hours different at most at any time. We know we will have to manually mount volumes and such if the primary facility gets destroyed.
Again, assuming we have line speeds and connectivity between the buildings they really can't tell they are 5 feed apart or 500 meteres apart.
With the above said. I'm trying to see why this would be a good or bad idea. At first glance, I see this a simple physical move of the box. The IP infrastructure will all stay the same. Again just thinking of the other building as an addition to our primary site just 500 meters away.
With our setup, is there any reason to invest in other software like DoubleTake Availability. I've seen demos of this and looks very interesting, but almost looks like its own version of Microsoft Clustering. Is this something we could leverage into our existing setup or is it completely unrelated and unnecessary.
Any info enlightening us on potential implications or pitfalls to certain issues splitting the cluster nodes into two facilities.