Excellent blog post from Elan Shudnow , Microsoft MVP and blogger.  Elan provides a very concise and compact post and much food for thought on new options, opportunities, and challenges for high availability and load balancing scenarios for Exchange 2010 RTM. 

Elan states, "In Exchange 2007, if you wanted any type of HA, you needed at least four servers.  2 for CCR Nodes and 2 for HUB/CAS Nodes.  The reason why you cannot have 2 nodes altogether is that CCR Nodes were limited to the Mailbox role only.  For an Exchange Site, you need to always have at least the  HUB/CAS/MBX Role  for that site to be operational.  In Exchange 2010, this was fixed.  You now have something called Database Availability Groups (DAGs).  These DAG members can contain all Exchange roles (HUB/CAS/MBX/UM) but still may not contain the Edge Transport role."

Elan points out a challenge though, he states. "There is a problem though.  There is a Windows limitation that allows you to install Windows Network Load Balancing on a server that also contains Failover Clustering Services. So while we can now have 2 Exchange 2010 Servers, we need a way to load balance the CAS role to provide High Availability for the following CAS Services"

You can read Elan's entire post by clicking here! 

Comments (0)

Show/hide comments

Write comment

Name

Email

Website

Comment

smaller | bigger

Subscribe via email (registered users only)

I have read and agree to the Terms of Usage.

Write the displayed characters

Add Comment Preview