Shijaz.com: Articles | Windows Server | Exchange Server | ISA Server |
How
to setup an Exchange 2003 cluster
|
Shijaz Abdulla, MVP |
This article explains how to setup a
two-node active-passive Exchange 2003 cluster on Windows 2003
Pre-requisites
To successfully complete the
procedures mentioned in the article, you need the following:
Step 1.
Installing a
Windows 2003 Cluster
1. Make sure that
all hardware & software prerequisites are met. Perform these steps on the
first node. Keep the second node powered off.
2. Install Cluster Administrator from Add/Remove
Programs à Add/Remove Windows Components.
3. Start Cluster Administrator (Start à
Administrative Tools à Cluster Administrator)
4. Select Create New Cluster and click OK.



5. Specify the
domain and cluster name.

6. Select the
name of the first node.
7. Choose Typical (full) configuration. Click Next.
8. Configuration
Analysis will run.

9. The Wizard
automatically associates the cluster IP address with one of the public
networks. Click Next.

10. Choose the
account for running the cluster service. (must be member of Administrators
group, Password never expires/User cannot change password)

11. See the
summary, and click Next. Cluster creation will proceed and notify you
of the completion.
Step 2.
Create MSDTC
Resource
1. Start Cluster Administrator (Start à
Administrative Tools à Cluster Administrator)
2. Create a new
group named “MSDTC Group” (File à New à Group)
3. Create an IP
Address resource:
i. Right-click MSDTC Group and choose New à Resource.
Give a descriptive name (like MSDTC IP
Address). Under Resource Type,
click IP Address, select MSDTC Group and click Next.
ii. In Possible Owners, select all nodes and
click Next.
iii. Under Dependencies, simply click Next.
iv. In TCP/IP Address Parameters, select the
public network. Type unique static IP address for MSDTC group. This should be
unique and unused (different from your cluster IP and your public IP).
v. Click Finish. Click OK.
4. Create a
Network name resource:
i. Right-click MSDTC Group and choose New à Resource.
Give a descriptive name (like MSDTC
Network name). Under Resource Type,
click Network Name, select MSDTC Group and click Next.
ii. In Possible Owners, select all nodes and
click Next.
iii. Under Dependencies, select MSDTC IP Address and click Next.
iv. Under Name, enter network name for the MSDTC
resource and click Next. This name will be used by the users to access the Exchange cluster.
v. Click Finish. Click OK.
5. Create a
Physical disk resource (if it does not already exist, else proceed to 6)
i. Right-click MSDTC Group and choose New à Resource.
Give a descriptive name (like MSDTC
Physical disk). Under Resource Type,
click Physical disk, select MSDTC Group and click Next.
ii. In Possible Owners, select all nodes and
click Next.
iii. Under Dependencies, simply click Next.
iv. Under Disk Parameters, select the disk that
you want to use for MSDTC.
v. Click Finish. Click OK.
6. Create the MSDTC
resource
i. Right-click MSDTC Group and choose New à Resource.
Give a descriptive name (MSDTC Resource).
Under Resource Type, click Distributed Transaction Co-ordinator,
select MSDTC Group and click Next.
ii. In Possible Owners, select all nodes and
click Next.
iii. Under Dependencies, select both MSDTC Physical Disk and MSDTC Network Name (which you just
created).
iv. Click Finish. Click OK.
v. Right click MSDTC Resource and choose Bring Online.
Step 3.
Install
Exchange 2003
1. Install
Exchange 2003 on each node.
2. Install hotfix 831464 on each node
if required.
3. Install
Exchange 2003 Service Pack 1 on each node.
Step 4.
Create
Exchange Virtual Server
1. Make sure all
resources are online. Right click on the Exchange cluster group and choose New Resource.
2. Specify a name
such as System Attendant. Select Microsoft Exchange System Attendant as
Resource Type.

3. Add the nodes
that will be possible owners to this resource. Add the nodes that you have
included in the cluster. These nodes can be “possible owners” meaning that
failover can take place on any of these nodes.

4. Set the
dependencies on the System Attendant Resource. The following are the
dependencies:
i. Network name
resource
ii. Disk Resources
that Exchange should use (If you want to keep logs an data on separate disks,
include two disks)

5. Select the
Administrative Group.

6. Choose the
Routing Group where the Exchange Virtual Server should reside within the
Administrative Group.

7. See the
summary carefully. Click Finish.

8. When the
process is complete you will be notified.

9. Once EVS is
created, the other Exchange resources are automatically created. But they will
all appear offline.

10. Bring online
the Exchange System Attendant
Resource you just created. To do this, right click the resource and choose Bring Online.

11. Your Exchange
2003 cluster is now ready. Thoroughly test failover. Enable failback if
required and test that too.
Migrating
from Exchange 5.5/2000 Standalone to Exchange 2003 cluster
Generally, migration from a standalone
to a cluster does not add much complexity to the scenario than a standalone to
standalone migration.
For most scenarios, simply set up the
Exchange cluster on new hardware and perform a normal migration. For more details
on migration strategies, see the migration section at www.shijaz.com/exchange.
Was
this Article Useful?
Related
Information
Cluster
Configuration Checklist from IT Showcase for Exchange 2003
http://www.microsoft.com/downloads/details.aspx?FamilyId=0E9B809D-2A7A-4ADF-9FDE-897210A461DB&displaylang=en
Guide
to Creating and Configuring a Server Cluster under Windows Server 2003
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/confclus.mspx
How
to configure Microsoft Distributed Transaction Coordinator on a Windows Server
2003 cluster
http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
High
Availability Guide for Exchange 2003
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/highavailgde.mspx
How
to install Exchange Server 2003 Service Pack 1 in a clustered Exchange
environment
http://support.microsoft.com/default.aspx?scid=kb;en-us;867624
Disclaimer
The steps mentioned in this are
results of testing in a lab environment. The procedure might require additional
testing before being deployed on a live environment. I assume no responsibility
for damage(s) occurring due to following this procedure or any other procedure
listed on this site. Use it at your own risk!