Exchange Server 2003 running on a physical Server want to add an Exchange cluster for failover

352485 pts.
Tags:
Exchange Cluster
Microsoft Exchange 2003
I have a MS Exchange Server 2003 running on a physical Server and would like to add an Exchange cluster server for failover. Is that possible?

Answer Wiki

Thanks. We'll let you know when a new response is added.

In versions before Exchange 2003 SP1, regardless of the number of cluster nodes you could only have one instance of a Public Folder store that is associated with the MAPI folder tree.

In Exchange 2003 SP1, the Exchange development team added the ability to have multiple MAPI Public Folder databases on a single multi node cluster.

This support was added because the Exchange team saw that Outlook 2003 cached mode puts a greater load on Public Folders like the Outlook Address Book (the OAB will be loaded offline at the client). With the help of multiple Public Folder stores the load can be spread across these folders. This allows a better client performance.
Why Active/Active cluster is not recommended

Active / Active cluster is not recommended because of Virtual memory (VM) fragmentation.
When two instances of the information store is running in one memory space, it might be possible that sufficient VM does not exist to bring the resource online during a failover/failback.

There are three main concepts which reduce virtual memory fragmentation:

* Decrease the number of dynamic allocations when the system is started
* Increase the size of the virtual address space
* Allocate similar size allocations from common regions of memory

Exchange Server 2003 Cluster Requirements

* Microsoft Windows 2000 Advanced Server (up to two nodes)
* Windows 2000 Datacenter Server (up to four nodes)
* Windows 2000 must have SP3 + 329938 hotfix or SP4
* Windows Server 2003, Enterprise Edition (up to eight cluster nodes)
* Windows Server 2003, Datacenter Edition (up to eight cluster nodes)
* Hardware on cluster HCL
* Windows 2000 – Check lists for cluster service installation.
* Windows Server 2003
* Microsoft Distributed Transaction Coordinator (MSDTC) installed

Exchange Server 2003 Cluster Setup Changes

* Block removal of node if an EVS is running on the cluster
* The /disasterrecovery switched is blocked
* Prevent Exchange 2003 from being first non-legacy server in a Exchange 5.5 site
* By default, POP3 and IMAP4 resource not created (as part of the Trustworthy Computing initiative from Microsoft)
* Cluster service account doesn’t requires Exchange full admin rights
* IPSEC is now supported between front-end servers and back-end clusters

Exchange Server 2003 Cluster Disk Changes

Windows 2003 clusters now support Volume Mount points to overcome the limits of traditional drive letter assignments. This new feature is very useful for four and eight node Exchange clusters because the traditional drive letter assignment in Exchange was very limited in cluster environments when multiple storage groups and stores where used.
Windows 2003 Cluster Setup

I will not explain every step for installing a Windows 2003 Cluster. For detailed information click the following link.

The Windows 2003 Cluster administrator after successful installation.

Exchange 2003 Cluster Setup

Before we install Exchange 2003, we must create a MS-DTC (Distribution Transaction Coordinator) resource.

In Windows 2003, Microsoft recommends installing the DTC as a separate Cluster Group containing a Physical Disk, Network Name and IP address resource and then adding the MSDTC resource to the cluster group.

For more in formation how to setup the MS-DTC in a Windows 2003 Cluster, read the following Knowledge Base article.

The second step is to install Exchange 2003 and all required hotfixes on each node. You MUST install Exchange one after the other. After installing Exchange, you can deploy Exchange 2003 SP1 on every cluster node. For more information on how to deploy Exchange 2003 SP1 into a cluster environment read the following article.

Once the Exchange 2003 binaries have been installed on the cluster Node we can now create an Exchange Virtual Server.

The Exchange Virtual Server creation process is much the same as for Exchange 2003. First we need to create a cluster group for the Exchange Virtual Server. The group must have at least one physical disk resource, at least one IP address resource, and a network name resource. The network name resource must have a dependency on the IP address resources in the cluster group.

When all resources are online, we must create the System Attendant resource. The System Attendant Resource (SA) creates all the other Exchange 2003 cluster resources automatically.

To do this, right click the Exchange 2003 cluster group and choose New Resource and then choose the Microsoft Exchange System Attendant. You must name the SA.

Add the Nodes that will be possible owners of the System Attendant Resource. A possible owner is a node in the cluster on which the resource can be brought online. These Nodes will also be added as a possible owner of all the other Exchange resources that are automatically created. A Node must be specified as a possible owner of a resource in order for us to failover to that Node.

You must set the dependencies on the System Attendant Resource. The dependencies are the following:

* Network Name resource
* All disk resources (that Exchange 2003 should use – this includes Mount Point disks which will contain Exchange 2003 data)

Like a normal Exchange installation you must select the administrative group where the Exchange virtual server is created.

Within the chosen Administrative Group you now have to choose a Routing Group where the Exchange Virtual Server will be located when more than one Routing Group exists at the time of EVS creation. You can change the server location in the Routing Group after installation.

Please read the wizard’s summary carefully.

Click Finish to start the creation process. This may take a while because the setup process actually creates all Exchange 2003 cluster resources. When the process is complete you will see the following message:

The following picture shows the Cluster Administrator tool after EVS installation. Note that all Exchange resources are NOT online.

Exchange 2003 no longer creates a POP3 and IMAP cluster resource. This is part of Microsoft’s Trustworthy initiative and it is also true for a “normal” Exchange 2003 installation.

Next, we have to bring the System Attendant resource online. To do so, right click the EVS System Attendant and click “Bring Online”.

Exchange 2003 Resource dependencies

Microsoft has changed the Exchange 2003 resource dependencies to allow a faster failover/failback.

In Exchange 2000 there are the following dependencies:
IP Address > Network Name > System Attendant
Physical Disk > System Attendant
Routing Engine > System Attendant
Information Store > System Attendant
MTA > System Attendant
MS Search > Information Store
POP3 > Information Store
SMTP > Information Store
IMAP4 > Information Store

Beginning with Exchange 2003 Microsoft has changed the Resource dependencies:
IP Address > Network Name > System Attendant
Physical Disk > System Attendant
Routing Engine > System Attendant
Information Store > System Attendant
MTA > System Attendant
MS Search > System Attendant
POP3 > System Attendant
SMTP > System Attendant
IMAP4 > System Attendant

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following