By default, if Exchange 2003 is clustered and there are more than 2 nodes in
the cluster, any node in the cluster will not be allowed to bring online
more than one EVS. If there is a failover of an EVS and there is no Passive
node available that is listed as a Possible Owner for EVS resources, then
that EVS will fail.
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.
<josh.boggis[ at ]gmail.com> wrote in message
news:1184266380.626676.29680[ at ]k79g2000hse.googlegroups.com...
[Quoted Text] >I have a 6 Node (4 active/2 passive) cluster going with Exchange 2003.
>
> Each exchange virtual server is in its own group.
>
> What I am trying to prevent is if two nodes fail they will not attempt
> to start on the same passive node. I've done some research on
> AntiAffinityClassNames, and have found it has been set by default with
> the cluster install. But I am very confused on its functionality.
>
>>From my interpretation from what I have read, the registry key for
> AntiAffinityClassNames should only have a string if that node is
> handling a group with AntiAffinityClassNames set. However I find this
> key on all nodes, active and passive.
>
> My goal in the end...with 4 active nodes (A,B,C,D) and two passive
> (E,F), if any active node fails, it does to E or F, whichever one
> isn't currently hosting another group. If E and F are hosting other
> groups then that node will just go offline.
>
> Is this possible?
>
|