|
|
|
date: Fri, 30 Nov 2007 12:57:00 -0800,
group: microsoft.public.exchange.clustering
back
Re: Cluster Group Configuration
The earlier recommendation was to add MSDTC to the Cluster group (which has
the cluster IP, network name and quroum disk resources) itself, iirc.
Something changed (again, iirc... :) after the following:
MSDTC Resource and Confusing KB 301600
http://exchangepedia.com/blog/2004/06/msdtc-resource-and-confusing-kb-301600.html
Adding MSDTC to a separate/own cluster group (i.e. other than the Cluster
group which has quorum), you need another IP address, network name, and a
disk resource for the MSDTC.
The advantage is - this does allow you to test failovers without impacting
anything at all... simply try failing over the MSDTC group first, then the
Cluster group. If those failover, it's very likely you won't have issues
with failing over any EVSes, imo.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------
"Marc J" wrote in message
news:29E4E306-5243-4EE3-AF61-EF58582EC66A@microsoft.com...
>I have an exchange cluster with one cluster group with all the resources
> within that group, including MSDTC. The exchange cluster is an
> active/passive cluster. It is recommended by MS that there be multiple
> groups for the resources. How is this accomplished since some resources
> have
> similar dependencies, and resources cannot use dependencies from another
> group? Also since it is recommended that the MSDTC resource be in another
> cluster group, how can there be two name resources and two IP resources?
>
> My quandary is that all the exchange resources depend on the System
> Attendant, while the System Attendant depends on Name Resource, and the
> Name
> Resource depends on the IP resource. How can these be separated into
> groups?
date: Fri, 30 Nov 2007 14:46:31 -0800
author: Bharat Suneja [MVP]
Re: Cluster Group Configuration
301600 talks about windows in general and covers a lot more cases than
Exchange. For example, if you have a SQL cluter, you'd want the DTC in a
seperate group. For Exchange, you can find the current guidance (for 2003)
in the High Availability guide; put the DTC in the default cluster group
with the quorum. Exchange 2003 only uses the dtc during install and
installation of service packs. For Exchange 2007, there is no requirement
for the DTC.
You should hae two groups. In the first group, the cluster management IP,
name, the quorum disk, and the msdtc resources. In the second group, the
exchange 2003 EVS IP, name, Exchange disks, and exchange services.
"Bharat Suneja [MVP]" wrote in message
news:OCQ9aL6MIHA.4948@TK2MSFTNGP02.phx.gbl...
> The earlier recommendation was to add MSDTC to the Cluster group (which
> has the cluster IP, network name and quroum disk resources) itself, iirc.
>
> Something changed (again, iirc... :) after the following:
> MSDTC Resource and Confusing KB 301600
> http://exchangepedia.com/blog/2004/06/msdtc-resource-and-confusing-kb-301600.html
>
> Adding MSDTC to a separate/own cluster group (i.e. other than the Cluster
> group which has quorum), you need another IP address, network name, and a
> disk resource for the MSDTC.
>
> The advantage is - this does allow you to test failovers without impacting
> anything at all... simply try failing over the MSDTC group first, then the
> Cluster group. If those failover, it's very likely you won't have issues
> with failing over any EVSes, imo.
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
>
>
> "Marc J" wrote in message
> news:29E4E306-5243-4EE3-AF61-EF58582EC66A@microsoft.com...
>>I have an exchange cluster with one cluster group with all the resources
>> within that group, including MSDTC. The exchange cluster is an
>> active/passive cluster. It is recommended by MS that there be multiple
>> groups for the resources. How is this accomplished since some resources
>> have
>> similar dependencies, and resources cannot use dependencies from another
>> group? Also since it is recommended that the MSDTC resource be in
>> another
>> cluster group, how can there be two name resources and two IP resources?
>>
>> My quandary is that all the exchange resources depend on the System
>> Attendant, while the System Attendant depends on Name Resource, and the
>> Name
>> Resource depends on the IP resource. How can these be separated into
>> groups?
>
date: Fri, 30 Nov 2007 16:19:42 -0800
author: John Fullbright fjohn@donotspamnetappdotcom
|
|
