Utilizing and Understanding Clustering for SharePoint


The operating system for SharePointWindows Server 2003provides two clustering technologies, Network Load Balancing (NLB) and the Microsoft Cluster Service (MSCS). NLB is available on the Standard version of the platform, whereas MSCS is only available on the Enterprise and Datacenter server platforms. Clustering is the grouping of independent server nodes accessed and viewed on the network as a single system. When an application is run from a cluster, the end user can connect to a single cluster node to perform his work, or each request can be handled by multiple nodes in the cluster. In cases where data is read-only, the client may request data and receive the information from all the nodes in the cluster, improving overall performance and response time.

Clustering technologies in Windows Server 2003 can help to scale SharePoint by allowing more resources to assist in the overall environment. For example, multiple network load balanced SharePoint front-end servers can distribute traffic to a clustered set of SQL database servers, as illustrated in Figure 22.2.

Figure 22.2. NLB-enabled front-end servers and clustered SQL database servers.


The first clustering technology Windows Server 2003 provides is Cluster Service, also known as Microsoft Cluster Service (MSCS). The Cluster Service provides system fault tolerance through a process called failover. When a system fails or is unable to respond to client requests, the clustered services are taken offline and moved from the failed server to another available server, where they are brought online and begin responding to existing and new connections and requests. Cluster Service is best used to provide fault tolerance for file, print, enterprise messaging, and database servers.

The second Windows Server 2003 clustering technology is NLB and is best suited to provide fault tolerance for front-end SharePoint servers. NLB provides fault tolerance and load balancing by having each server in the cluster individually run the network services or applications, removing any single points of failure.

NOTE

Microsoft does not support running both MSCS and NLB on the same computer due to potential hardware sharing conflicts between the two technologies.


Understanding the Active/Passive Clustering Mode

Active/passive clustering occurs when one node in the cluster provides clustered services while the other available node or nodes remain online but do not provide services or applications to end users. When the active node fails, the cluster groups previously running on that node are failed over to the passive node, causing the node's participation in the cluster to go from passive to active state to begin servicing client requests.

This configuration is usually implemented with database servers that provide access to data that is stored in only one location and is too large to replicate throughout the day. One advantage of Active/Passive mode is that if each node in the cluster has similar hardware specifications, there is no performance loss when a failover occurs. The only real disadvantage of this mode is that the passive node's hardware resources cannot be leveraged during regular daily cluster operation.

NOTE

Active/passive configurations are a great choice for keeping cluster administration and maintenance as low as possible. For example, the passive node can be used to test updates and other patches without directly impacting production. However, it is nonetheless important to test in an isolated lab environment or at a minimum, during after hours or predefined maintenance windows.


Understanding the Active/Active Clustering Mode

Active/active clustering occurs when one instance of an application runs on each node of the cluster. When a failure occurs, two or more instances of the application can run on one cluster node. The advantage of Active/Active mode over Active/Passive mode is that the physical hardware resources on each node are used simultaneously. The major disadvantage of this configuration is that if you are running each node of the cluster at 100% capacity, in the event of a node failure, the remaining active node assumes 100% of the failed node's load, greatly reducing performance. As a result, it is critical to monitor server resources at all times and ensure that each node has enough resources to take over the other node's responsibilities if the other should fail over.




Microsoft SharePoint 2003 Unleashed
Microsoft SharePoint 2003 Unleashed (2nd Edition) (Unleashed)
ISBN: 0672328038
EAN: 2147483647
Year: 2005
Pages: 288

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net