Using Windows Clustering

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

Windows Clustering provides a higher level of fault tolerance but consumes additional system resources. If your business goals require a WINS design that provides the highest availability, use server clusters as provided by Windows Clustering. By configuring WINS on multiple servers belonging to the same cluster, you:

  • Share a common WINS database.

  • Provide immediate failover in the event of failure.

  • Restore failed servers sooner, because database resynchronization is not required between the cluster nodes.

Note

  • If you choose to cluster your WINS servers, be sure to equip the servers with a hard disk containing high-speed I/O that is dedicated to WINS. This can speed up the database response and ensure clustering efficiency.

Example: A Company Uses a Cluster to Simplify their WINS Design

A large corporation uses a server cluster to provide infrastructure services, including WINS. Prior to implementing the server cluster, the company had a large and complicated Windows NT 4.0–based WINS replication topology. To maintain consistency and provide accurate information to clients, WINS client records were replicated to all WINS servers.

To simplify the replication matrix, provide redundancy, and more efficiently manage the WINS traffic load, a server cluster is used as the WINS replication hub. Applications and services running on nodes in the cluster are exposed to users and workstations as virtual servers. Figure 4.3 shows the replication matrix before the WINS cluster implementation.

Figure 4.3   WINS Topology Pre-Clustering

WINS Topology Pre-Clustering

Figure 4.4 shows the new simplified replication matrix using a server cluster.

Figure 4.4   WINS Topology Post-Clustering

WINS Topology Post-Clustering

Windows Clustering only solves local availability issues. Windows Server 2003–based servers that belong to the same cluster require persistent, high-speed connections between all servers in the cluster.

Note

  • Before adding WINS to a set of clustered servers, be sure to consider both the advantages and disadvantages of doing so. In many cases, the overall number of WINS servers is small, so clustering WINS is not necessary — replication makes WINS fault tolerant. Instead, configure your WINS clients with the address of a secondary WINS server to ensure uninterrupted service.

For more information about server clusters, see "Designing and Deploying Server Clusters" in Planning Server Deployments of this kit.

Caution

  • WINS does not support rolling upgrades from Windows 2000 to Windows Server 2003 in a server cluster. You can upgrade and failover to Windows Server 2003. However, when WINS is brought online on Windows Server 2003, it cannot fail back to the Windows 2000 node.