5 replies
by lahrens Accepted solution
by robo_dev Accepted solution
Yes,sort of, using Microsoft Clustering.
But, if you're talking straight "exchange-on -VMware", Microsoft does not support that, but it may work...which means you would be on your own if something breaks.
See some of the links below to clarify:
www.vmware.com/pdf/exchange_best_practices.pdf
http://technet.microsoft.com/en-us/library/bb123612(EXCHG.65).aspx
by lahrens Accepted solution
by robo_dev Accepted solution
But, I my experience with Microsoft apps and databases in general tells me to watch out for some 'gotchas' with respect to database replication, message loss, etc.
So my only caution would be to use a configuration that somebody else has used before...don't be the guinea pig.
http://technet.microsoft.com/en-us/magazine/2006.10.failoverclusters.aspx
by churdoo Accepted solution
Seems to me that one looking for High Availability of Exchange would use VMWare HA/DRS OR MS Clustering (MSCS), but curious why you would want to cluster a physical with a virtual within the cluster. This may add a level of complexity and a new set of pitfalls to something already potentially hairy. Nonetheless, MSCS is supported in ESX 3.5 update 1, so what you're suggesting "should" work I suppose if you have the right version of ESX, though I would approach with caution. And if you do have the right version of ESX, then maybe the VMWare HA/DRS will be sufficient for you.
Which parts of Exchange do you need the High Availability for? Is it for email delivery or Outlook connections for example? Which HA or failover option you choose depends an what resources you have and which components of Exchange need high availability.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending