MS SQL Server
  Home arrow MS SQL Server arrow Page 13 - 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) - Testing Clusters


    (Page 13 of 26 )

    After all the desired cluster nodes are added and failover and failback are configured for each cluster group to complete cluster installation, it is time to test cluster functionality. For these tests to be complete, failover and, when applicable, failback of cluster groups need to be tested. They can be tested by manual failover and also by taking a cluster node off the network by unplugging network cards. However, the cluster is not tested by disconnecting shared storage device connections because this may cause possible corruption in the shared storage data.


    Note - Clusdiag.msi, located in the Windows Server 2003 Resource Kit, can be used to diagnose and test the cluster. It can also aid in troubleshooting failures by providing administrators reports based on prior testing.


    Morimoto

    Figure 31.10 Setting failback for a cluster file group.

    Testing Cluster Group Manual Failover

    To test the cluster group failover manually, follow these steps:

    1. Open Cluster Administrator, right-click the desired cluster group, and choose Take Offline.

    2. Right-click the same cluster group and choose Move Group. If the cluster contains more than two nodes, choose the node to which you want to move the group.

    3. Right-click the same cluster group and choose Bring Online.

    4. The group now should start on the node you chose in step 2. Repeat steps 1–3 for each cluster group, moving back and forth between all available cluster nodes.

    5. When testing is complete, move cluster groups to their desired cluster nodes and bring all groups online.

    Initiating Failure of a Cluster Resource

    To simulate a cluster resource failure, a cluster administrator can initiate a resource failure using the Cluster Administrator utility. This utility can be used to verify how a failing cluster resource will affect the cluster group.

    To test the failure of a cluster resource, follow these steps:

    1. Open Cluster Administrator.

    2. Right-click the cluster resource you will manually fail and select Properties.

    3. Select the Advanced tab and note how many failures this resource will tolerate before it finally fails completely or fails the entire cluster group.

    4. Close the resource's property page.

    5. Right-click the cluster resource you will manually fail and choose Initiate Failure.

    6. Repeat the preceding steps as necessary to ensure proper operation during resource failure conditions.

    7. When testing is complete, move cluster groups to their desired cluster nodes and bring all groups online.

    Initiating Cluster Node Network Failure

    To simulate and verify how cluster groups will fail over during a cluster node network or network card failure, perform the following steps:

    1. Log on to the desired cluster node with Cluster Administrator or Local Administrator permissions.

    2. Click Start, Control Panel.

    3. Double-click the Network Connections applet.

    4. Right-click each of the cluster node's private network and public network adapters and choose Disable.

    5. On an available cluster node, log in using a Cluster Administrator account.

    6. Click Start, Administrative Tools, Cluster Administrator.

    7. If the Cluster Administrator does not connect to the cluster or connects to a different cluster, choose File, Open Connection.

    8. From the Active drop-down box, choose Open Connection to Cluster. Then, in the Cluster or Server Name drop-down box, type . (period) and click OK to connect.

    9. Verify that the network-disabled node appears as offline and that all cluster groups have failed over to other available cluster nodes.

    10. When testing is complete, enable all disabled network cards on the network-disabled node.

    11. Move cluster groups to their desired cluster nodes and bring all the groups online.

    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 3 hosted by Hostway
    Stay green...Green IT