MS SQL Server
  Home arrow MS SQL Server arrow Page 25 - System-Level Fault Tolerance (Clustering/N...
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Mobile Linux 
App Generation ROI 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
MS SQL SERVER

System-Level Fault Tolerance (Clustering/Network Load Balancing)
By: Sams Publishing
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 15
    2004-09-22

    Table of Contents:
  • System-Level Fault Tolerance (Clustering/Network Load Balancing)
  • Choosing Networking Hardware for Fault Tolerance
  • Examining Windows Server 2003 Clustering Technologies
  • Active and Passive Clustering Modes
  • Choosing the Right Clustering Technology
  • Implementing Cluster Service
  • An MNS Cluster Scenario
  • Shared Storage Devices
  • Installing Cluster Service
  • Installing the First Node in the Cluster
  • Adding Additional Nodes to a Cluster
  • Cluster Group Failover Configuration
  • Testing Clusters
  • Maintaining Cluster Nodes
  • Creating Additional Cluster Groups and Resources
  • Removing a Node from a Cluster
  • Cluster Node Backup Best Practices
  • Backing Up the Cluster Node System State
  • Restoring a Single-Node Cluster When the Cluster Service Fails
  • Restoring a Single Node After a Complete Server Failure
  • Restoring an Entire Cluster to a Previous State
  • Restoring Cluster Nodes After a Cluster Failure
  • Installing Network Load Balancing Clusters
  • Using the Network Load Balancing Manager to Create a Cluster
  • Managing NLB Clusters
  • Summary and Best Practices

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    System-Level Fault Tolerance (Clustering/Network Load Balancing) - Managing NLB Clusters


    (Page 25 of 26 )

    A cluster can be managed using the NLB Manager or the NLB.exe command-line utility. Using the NLB Manager, a node can be added, removed, or suspended from cluster operation to perform maintenance, including hardware or software updates. Because data is not replicated between cluster nodes, any data needs to be replicated manually or by using tools such as Robocopy.exe, which are located in the Windows Server 2003 Resource Kit.


    Note - Network activity for NLB clusters can be monitored using the Network Monitor and parsers provided in the Windows Server 2003 Resource Kit. These parsers are called Wlbs_hb.dll and wlbs_rc.dll.


    Backing Up and Restoring NLB Nodes

    The procedure for backing up and restoring NLB nodes is no different than for standalone servers. An ASR backup should be created after any major server configuration change, and the local disks and system state of each node should be backed up regularly (weekly). An NLB configuration can be restored when the system state of a particular node is restored. If a full node recovery is necessary, the system state and local disks should be restored or an ASR restore should be performed. For detailed backup and restore procedures, refer to Chapters 32 and 33 and follow procedures for backing up and restoring standalone servers.

    Performing Maintenance on a Cluster Node

    To perform maintenance on an NLB cluster node, the administrator can temporarily remove the node from the cluster, perform the upgrade, and add it back in later. Removing the node from the cluster without affecting user connections requires the use of the drainstop option from the Network Load Balancing Manager. The drainstop option tells the cluster to take this node offline and immediately stop connecting new clients to this node. Existing sessions will remain active until they are all closed. When all the sessions are complete, maintenance can be performed, and the server can be made available in the cluster to start accepting user requests.

    To perform maintenance on a cluster node, follow these steps:

    1. Log on to a workstation or server that has the Windows Server 2003 Administrative Tools installed.

    2. Click Start, All Programs, Administrative Tools and right-click Network Load Balancing Manager.

    3. Choose the Run-as option and specify an account that has Administrative permissions on the cluster.

    4. Choose Cluster, Connect to Existing.

    5. In the Host text box, type the IP address or name of the cluster and click Connect.

    6. From the Clusters window, select the cluster you want to connect to and click Finish to connect.

    7. Each node in the cluster should appear with a green background, signifying operational status. Right-click the node to perform maintenance and select Control Host, Drainstop, as shown in Figure 31.22.

      Morimoto

      Figure 31.22 
      Selecting the Control Host, Drainstop option.

    8. When the node is draining, it should have a half-red and half-green background, and the drainstop operation result should be listed in the log window. Right-click the draining cluster node and select Host Status.

    9. Refer to the summary status to verify that the node is draining and then click OK to close this window.

    10. After you complete all connections on this node, the node will turn red. Perform any necessary maintenance.

    11. When maintenance is complete, if no reboots are necessary, in the NLB Manager, right-click the node and choose Start. If a reboot is necessary, the node will rejoin the cluster according to Initial Host State settings on the Host property page. Change the Initial Host State settings as necessary to achieve the desired node effect according to the type of maintenance that is being performed.

    12. When the node completes rejoining the cluster, it should have a green background in the NLB Manager window.

    13. Click File, Close to exit the Network Load Balancing Manager utility.

    Removing a Node from an NLB Cluster

    To remove an existing node from a cluster, follow the steps up to step 10 in the "Performing Maintenance on a Cluster Node" section. Then do the following:

    1. Right-click the node and choose Delete Host.

    2. A warning message pops up stating that this action will remove the node from the cluster. Click the Yes button to remove the node.

    Deleting the Entire Cluster

    To delete an entire cluster, follow the procedure in the "Performing Maintenance on a Cluster Node" section on each node in the cluster. When all nodes are red, indicating a stopped status, right-click the cluster name and choose Delete Cluster, as shown in Figure 31.23.

    Morimoto

    Figure 31.23 
    Deleting a cluster.

    This chapter is from Microsoft Windows Server 2003 Unleashed, by Rand Morimoto, et al. (Sams Publishing, 2004, ISBN: 0672326671). Check it out at your favorite bookstore today.

    Buy this book now.

    More MS SQL Server Articles
    More By Sams Publishing


     

    MS SQL SERVER ARTICLES

    - Completing the Introduction to Transact-SQL
    - A Brief Introduction to Transact-SQL
    - Lookups and Blocking Bad Data
    - Field Validation Rules for Blocking Bad Data
    - Using Masks to Block Bad Data
    - Blocking Bad Data
    - Using @@ROWCOUNT and TABLE Variables for Dat...
    - How to Use Variables, IF and CASE in Databas...
    - Creating Important Aspects of Notification S...
    - Working wth Variables in Database Interactio...
    - Delving Deeper into Notification Services
    - Notification Services
    - Building a Multi-table Report with SQL 2005 ...
    - A Secure Way of Building Connection Strings
    - Transferring a Database Using the SSIS Desig...





    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 6 hosted by Hostway
    Stay green...Green IT