Deployment Checklist for Cluster Continuous Replication on Windows Server 2003

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

Use this checklist to deploy cluster continuous replication (CCR) using the release to manufacturing (RTM) version of Microsoft Exchange Server 2007 or Exchange 2007 Service Pack 1 (SP1) on Windows Server 2003. This checklist is organized by each phase of the deployment process, as described in the topic, Installing Cluster Continuous Replication on Windows Server 2003.

Network Formation and Configuration

Static Internet Protocol Version 4 (IPv4) addresses for each node, the cluster, and the clustered mailbox server	Check
You have the required number of static IPv4 addresses. Use the following table to record the IP addresses that will be used in the CCR environment. Following the empty table is an example table that illustrates how to fill in the empty table.	[ ]

Table to record IP addresses used in the CCR environment

Address used by	Network name	Cluster network (public, mixed, or private)	IP address	Subnet mask
First node/First network
First node/Second network
Second node/First network
Second node/Second network
Cluster
Clustered mailbox server

Example of completed table of IP addresses used in the CCR environment

Address used by	Network name	Cluster network (public, mixed, or private)	IP address	Subnet mask
First node/First network	NODEA	Mixed	191.78.32.30	255.255.224.0
First node/Second network	NODEA	Private	10.10.10.10	255.255.255.0
Second node/First network	NODEB	Mixed	191.78.32.31	255.255.224.0
Second node/Second network	NODEB	Private	10.10.10.11	255.255.255.0
Cluster	EXCLUS1	Mixed	191.78.32.25	255.255.224.0
Clustered mailbox server	EXCCRMBX1	Mixed	191.78.32.26	255.255.224.0

Forming the Cluster

Creating the failover cluster, verifying the status of the default cluster group, and adding the second node	Check
The computers that will be the two nodes in the failover cluster are running a minimum of Windows Server 2003 SP1, plus the hotfix from Microsoft Knowledge Base article 921181, An update is available that adds a file share witness feature and a configurable cluster heartbeats feature to Windows Server 2003 Service Pack 1-based server clusters (if you are deploying the RTM version of Exchange 2007), or a minimum of Windows Server 2003 Service Pack 2 (SP2) (if you are deploying Exchange 2007 SP1.	[ ]
The new failover cluster for the CCR environment is built using the instructions in the topic, How to Create a Windows Server 2003 Failover Cluster for Cluster Continuous Replication.	[ ]
After the failover cluster has been formed, but before the second node has been added, the status of the default cluster group is verified. This is done by running the following command to verify that the default cluster group has a status of Online: Cluster group	[ ]
The second node in the new failover cluster has been added using the instructions in the topic, How to Create a Windows Server 2003 Failover Cluster for Cluster Continuous Replication.	[ ]

Post-Installation Tasks for the Failover Cluster

Configuring the cluster networks, tolerance for missed cluster heartbeats, and the file share witness	Check
Cluster networks are configured as private and mixed to avoid a network single point of failure for the clustered mailbox server (CMS). Cluster network priority is also configured. Both tasks are accomplished using the instructions in the topic, How to Configure the Cluster Networking Components and Priority.	[ ]
Cluster nodes are configured with tolerance for 10 missed heartbeats (12 seconds) using the instructions in the topic, How to Configure Tolerance Settings for Missed Cluster Heartbeats. The cluster's existing Majority Node Set (MNS) quorum is configured to use the file share witness using the instructions in the topic, How to Configure the File Share Witness.	[ ]

Clustered Mailbox Server Installation

Installing the active node, optionally relocating the first storage group to an alternate location, and installing the passive node	Check
The active CMS role is installed using the instructions in the topic, How to Install the Active Clustered Mailbox Role in a CCR Environment on Windows Server 2003.	[ ]
After the active node is installed, but before the passive node is installed, the first storage group can be moved to an alternate location using the instructions in the topic, How to Move a Storage Group and Its Database in a CCR Environment.	[ ]
The passive CMS role is installed using the instructions in the topic, How to Install the Passive Clustered Mailbox Role in a CCR Environment on Windows Server 2003.	[ ]

Post-Installation Tasks for the Clustered Mailbox Server

Tuning failover control settings, configuring the transport dumpster, verifying the ability to move the CMS, and optionally creating redundant mixed networks for continuous replication	Check
The AutoDatabaseMountDial parameter is configured using the instructions in the topic, How to Tune Failover and Mount Settings for Cluster Continuous Replication.	[ ]
The transport dumpster is configured using the instructions in the topic, How to Configure the Transport Dumpster.	[ ]
The health and status of the CMS is verified using the instructions in the topics, How to View the Status of a Storage Group in a CCR Environment and How to View the Status of a Clustered Mailbox Server.	[ ]
The ability to successfully hand off the CMS between nodes is verified using the instructions in the topic How to Move a Clustered Mailbox Server in a CCR Environment.	[ ]
One or more additional mixed networks are enabled for continuous replication activity using the instructions in the topic How to Enable Redundant Cluster Networks for Log Shipping and Seeding on Windows Server 2003.	[ ]