Even since Microsoft Exchange added clustering support, Exchange practitioners have always added a little asterisk when discussing its clustering capabilities.  Exchange 2000 clustering had significant resource consumption issues, with Active/Active clustering especially, and there was a time when it was simply not recommended.  That means Active/Passive clustering, also known as an expensive "spare tire".  A passive node sits in the cluster, waiting "just in case" of node failure.  In Exchange, this Active/Passive node couldn't do anything about failure at the shared disk, which left a single point of failure anyway.  

Apparently, the white flag is in full view at Microsoft TechEd Europe:

I'm in a Exchange clustering session now, the speaker just told the best practices on choosing active/active or active/passive scenarios for Exchange clustering.

I knew MS had active/active issues with Exchange clustering, I brought that in the open 4 years ago: http://veryold.bink.nu/exchange_2000.htm Big Smile [:D]

Now Microsft highly discourages active/active scenarious, saying if you have that running switch to a active/passive solution. In Exchange 12 active/active support will even not be available!Surprise [:O]
or, one supposes, you could switch to a Lotus Domino active/active solution, running Domino Access for MS-Outlook.  Another case where Lotus Domino improves your Outlook.....
Link: Bink.nu: TechEd Update: No Active/Active Fail-over cluster support in Exchange 12 > (via vowe.net)

Post a Comment

  1. 1  Darren http://www.dadams.co.uk |

    This sounds like an admission from Microsoft that they can't get the clustering right. So follow the logic thru... if they can't fix it with the current architecture, will they have to move Exchange to another architecture? If they do that, will it mean another migration scenario for customer post-Exchange 12? I know where my money would go.

  1. 2  Philip Storry http://www.not-so-rapid.com |

    Exchange doesn't cluster well. And in other news, the Pope's Catholic...

    What amazes me isn't that this is coming up again, it's that Microsoft can come out and say that high availability email is "still too complex" ({ Link } courtesy of yourself no less!), and keep saying it, and NOBODY SEEMS TO CARE.

    It's the Jobs Reality Distortion Field effect, but for CIOs.

    "Don't worry about high availability. We can't provide it, and you don't need it - you wouldn't be looking at Exchange Server otherwise, would you?"