Upgrading a 2 node A/P exchange 2003 cluster to a 4 node AAA/P cluster   

I was wondering if anyone has experience of upgrading (well expanding is 
another term) a W2k3, e2k3 (All Current Service Packs) 2 node exchange 
cluster to a 4 node AAA/P cluster.

We currently run 11 databases 4 storage groups on the 2 node cluster.

Any pitfalls on this path, considering it is a production server with about 
600 users on it at present and any operations carried out should not impact 
the current user base.

Is it just simpler (lesk risk) to add another 2 node A/P cluster and manage 
2 clusters rather than upgrading the current cluster to 4 nodes, thus 
getting 2 failover nodes.

Or is the process as stated in 
http://technet.microsoft.com/en-us/library/bb124864(EXCHG.65).aspx which 
leads back to the exchange deployment guide for installing on a cluster "the 
way"

The reality is we are planning for Exchange 2007 from next year, but need to 
consolidate a couple more servers before this to get to the end of the 
current year.


Any information welcomed

TIA
Rgds
Steve S

date: Wed, 7 May 2008 12:13:47 +0100   author:   Steve_S am

Re: Upgrading a 2 node A/P exchange 2003 cluster to a 4 node AAA/P cluster   

You can easily add nodes to an existing cluster.

Add 2 additional nodes to the same cluster:
- minimize the additional deployment/management overhead.
- Using an A/A/A/P topology, you can have up to 3 EVSes
- will have only 1 node available for failover
- as a sidenote, depending on number of Storage Groups you create and how 
these are located (DB + logs), you may run into drive letter limitations. 
Look at using volume mount points.

Create an additional 2-node cluster:
- one more cluster group (IP address + network name + quorum) and associated 
deployment/management overhead.
- Using an Active/Passive topology, you will be limited to 2 EVSes (1 EVS in 
each 2-node cluster)
- If a cluster is unavailable, a smaller set of users will be impacted.
-- 
Bharat Suneja
Microsoft Corporation
----------------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.


"Steve_S" <Steve_S@community.nospam> wrote in message 
news:%23$ZIuNDsIHA.5724@TK2MSFTNGP06.phx.gbl...
>I was wondering if anyone has experience of upgrading (well expanding is 
>another term) a W2k3, e2k3 (All Current Service Packs) 2 node exchange 
>cluster to a 4 node AAA/P cluster.
>
> We currently run 11 databases 4 storage groups on the 2 node cluster.
>
> Any pitfalls on this path, considering it is a production server with 
> about 600 users on it at present and any operations carried out should not 
> impact the current user base.
>
> Is it just simpler (lesk risk) to add another 2 node A/P cluster and 
> manage 2 clusters rather than upgrading the current cluster to 4 nodes, 
> thus getting 2 failover nodes.
>
> Or is the process as stated in 
> http://technet.microsoft.com/en-us/library/bb124864(EXCHG.65).aspx which 
> leads back to the exchange deployment guide for installing on a cluster 
> "the way"
>
> The reality is we are planning for Exchange 2007 from next year, but need 
> to consolidate a couple more servers before this to get to the end of the 
> current year.
>
>
> Any information welcomed
>
> TIA
> Rgds
> Steve S
>

date: Wed, 7 May 2008 08:25:23 -0700   author:   Bharat Suneja [MSFT]

Re: Upgrading a 2 node A/P exchange 2003 cluster to a 4 node AAA/P cluster   

Also if you are using a cross over cable currently for heartbeat 
functionality, you will have to move to a switch (or vLAN off some ports in 
an existing switch) to dedicate for a heartbeat lan.

If you are comfortable with it, I would go with the AAA/P configuration, the 
benefits mainly being a third EVS.

Oliver

date: Wed, 7 May 2008 17:32:48 +0100   author:   Oliver Moazzezi [MVP]

Re: Upgrading a 2 node A/P exchange 2003 cluster to a 4 node AAA/P cluster   

Bharat and Oliver.,

Thank you very much for the points raised much appreciated.

Kind Rgds
Steve



"Oliver Moazzezi [MVP]"  wrote in message 
news:OP3q$$FsIHA.5872@TK2MSFTNGP04.phx.gbl...
> Also if you are using a cross over cable currently for heartbeat 
> functionality, you will have to move to a switch (or vLAN off some ports 
> in an existing switch) to dedicate for a heartbeat lan.
>
> If you are comfortable with it, I would go with the AAA/P configuration, 
> the benefits mainly being a third EVS.
>
> Oliver
>

date: Wed, 7 May 2008 18:50:08 +0100   author:   Steve_S am