Cost Effective Method to Achieve Redunancy/Failover for standalone Exchange
Posted on 2010-09-17
We have a standalone Exchange 2007 server setup in-house, combined with a few other physical servers that take care of the rest of the services (file sharing, DC, DNS, DHCP, etc). The server recently froze and caused us a few hours of downtime until we were able to respond. Because of this I have begun looking into options for redundancy and failover and Server 2008 with Hyper V seems to be a good bet, but I wanted the input of some experts if possible.
Our environment is as follows:
1 physical 32 bit Windows Server 2003, performing DC, DNS, WINS
1 physical 32 bit Windows Server 2003, secondary DC, DNS, BES
1 physical 64 bit Windows Storage Server 2003, file sharing
1 physical 64 bit Windows Server 2003, Exchange 2007, WSS 3.0
Our end goal is to have services that can failover if needed and stay up and running. My current plan is to turn each physical server into VHD's that can be loaded into Server 2008 Hyper V. I'll then be wiping the 4th server in the list and installing Server 2008 with Hyper V. From there I imagine I can load all the VHD's, but that then gives me a single point of failure if that hardware goes down. I've seen software that can replicate VHD's to another box running Server 2008 Hyper V, but is that the best and most cost effective solution to achieve this?