| Clustering in Windows Server 2008

Clustering in Windows Server 2008

Clustering-in-Windows-Server-2008

A computer cluster is a group of loosely coupled computers that work together closely so that in many respects they can be viewed as though they are a single computer.

The components of a cluster are commonly, but not always, connected to each other through fast local area networks.

Clusters are usually deployed to improve performance and/or availability over that provided by a single computer, while typically being much more cost-effective than single computers of comparable speed or availability.

In Windows Server 2008, there are changes to the way clustering is configured.

High-availability (HA) clusters

High-availability clusters (also known as failover clusters) are implemented primarily for the purpose of improving the availability of services which the cluster provides.

They operate by having redundant nodes, which are then used to provide service when system components fail. The most common size for an HA cluster is two nodes, which is the minimum requirement to provide redundancy.

HA cluster implementations attempt to manage the redundancy inherent in a cluster to eliminate single points of failure.

There are many commercial implementations of High-Availability clusters for many operating systems.

Load-balancing clusters

Load-balancing clusters operate by having all workload come through one or more load-balancing front ends, which then distribute it to a collection of back end Platform LSF HPC, Sun Grid Engine, Moab Cluster Suite and Maui Cluster Scheduler.

The Linux Virtual Server project provides one commonly used free software package for the Linux OS.

The following items address clustering in Windows Server 2008:

Centralized web farm configuration in Windows Server 2008

Failover Clustering: the Quorom model for Windows Server 2008