Best Practices for Server Clusters

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

This section describes best practices for deploying a server cluster.

Planning Your Cluster

Before designing your cluster, analyze how your messaging system is used and design your cluster in a way that will accommodate peak usage periods. For example, the entire configuration of the server cluster that is discussed in this document (hardware, software and cluster configuration) is designed to meet the requirements for peak usage. At Microsoft, Monday mornings are the busiest time for e-mail, as employees attempt to catch up from the weekend. Every server cluster configuration should accommodate the peak usage periods.

Planning the Hardware for Your Cluster

  • Use identical network adapters in all cluster nodes. Each adapter should be the same make, model, and firmware version.

  • Reserve one network exclusively for internal communication between cluster nodes. This is the private network. Use other networks for communication with clients. These are public networks. Having two networks ensures that the network will be available for internal cluster communications.

  • Do not use teaming network adapters on the private network. Teaming network adapters, which are network adapters that are grouped on multiple ports to a single physical network segment, are used to provide fault tolerance.

  • Create a standard naming system for your resources, nodes, disks, IP Addresses, and backup sets. This will increase clarity for anyone working with the cluster.

Configuring the Network Adapters

  • Use static IP addresses for all nodes on the private network.

  • Use static IP addresses for all nodes on all public networks. We do not recommend using dynamic configuration with Dynamic Host Configuration Protocol (DHCP). Failure to renew a lease of an IP Address could disrupt cluster operation.

  • Do not configure DNS servers, WINS servers, or a default gateway on the private network adapters.

  • Configure WINS or DNS servers on the public network adapters. If network name resources will be deployed on the public network, then the DNS servers should support dynamic updates.

  • In Cluster Administrator, set the network connection order for each node to be:

    • Private network highest priority

    • Public network(s)

    • Remote access connections lowest priority

  • Change the default name for each network connection to clearly identify the use of each network. For example, you might change the name of the private network connection from Local Area Connection (x) to Private Cluster Network.

  • Isolate the internal network from public network communication. Only nodes that are part of the cluster should be connected to the private subnet. Where there are several clusters, using the same subnet for the private network for all of the clusters is reasonable.

Configuring the Cluster Service

  • Set the private network role to Internal cluster communications only. Verify that the role for each public network is set to All communications, which is the default value. These settings are available in Cluster Administrator.

  • In Cluster Administrator, configure the private network to be the highest priority for internal cluster communication. In addition, make sure the Public network is first in the TCP/IP Binding Order.

More Information