We help IT Professionals succeed at work.

Install/Mirgate Exchange Server 2003

Treadstone21
Treadstone21 asked
on
I am planning to implement redundancy in an exchange environment for a single server (within the environment).

The current is 7 years old. We have 2 new physical servers. I want to move the mailboxes and exchange service to the new physical servers and cluster it.
 
Would it be safe to say that the scoop of work is the following:

1. Install Exchange Server 1 into the current environment.

2. Move Mailboxes to exchange 1.

3. Install and configure cluster on exchange server 1.
4. Add exchange server 2 to the environment.

5 Install and configure cluster on exchange server 2.

Does that look about right?
Is there a step I missed or should I arrange them in a different order?

Can I install both servers at 1 time or should I install right after the other like I have it there?
Comment
Watch Question

Solutions Architect
Commented:
In exchange 2003 you cannot build clustering/HA after installation this is something you need to do during installation

so it should be more like

1) Install Exchange 2003 cluster on the 2 new servers
2) move all mailboxes / public folder etc.. to the cluster
3) decomission the curernt server

Author

Commented:
In this article:
http://msmvps.com/blogs/clusterhelp/archive/2005/08/05/common-exchange-2003-cluster-questions-top-11-list-original-posted-may-1-2005.aspx
 
It states that I need this many IP addresses:
NodeA Public Interface
NodeA Private Interface (for heart beat)
NodeB Public Interface
NodeB Private Interface (for heart beat)
Default Cluster Group (IP is needed as dependency for network name resource)
Exchange Virtual Server (IP is needed as dependency for network name resource for your EVS). You will need one IP for each EVS in your cluster.
 
We get our ip addreses from the domain controller (dhcp).
So should I request 6 static ip addresses then? Or just 4 (for the 2 Public interfaces, the default cluster group and the EVS)?
AkhaterSolutions Architect

Commented:
You will need IP from your network for

NodeA Public Interface
NodeB Public Interface
Default Cluster Group (IP is needed as dependency for network name resource)
Exchange Virtual Server (IP is needed as dependency for network name resource for your EVS).
(optional) You will need one IP for each EVS in your cluster.

so 4 depending on the above if you need only one EVS

your heart-beat network is on a different network this is the way it has to be