This paper discusses troubleshooting and maintenance techniques for the first implementation of Microsoft Cluster Server (MSCS) version 1.0. The initial phase of the product supports a maximum of two servers in a cluster, which are often referred to as nodes. Since there are so many different types of resources that may be managed within a cluster, it may be difficult at times for an administrator to determine what component or resource may be causing failures. In many cases, MSCS can automatically detect and recover from server or application failures. However, in some cases, it may be necessary to troubleshoot attached resources or applications.
The term clustering has been used for many years within the computing industry. Clustering is a familiar subject to many users, and seems very complicated, based on earlier implementations that were large, complex, and sometimes difficult to configure. Earlier clusters were a challenge to maintain without extensive training and without an experienced administrator.
Microsoft has extended the capabilities of the Microsoft Windows NTŪ Server operating system through the Enterprise Edition. Microsoft Windows NT Server, Enterprise Edition, contains Microsoft Cluster Server (MSCS). MSCS adds clustering capabilities to Windows 2000, to achieve high availability, easier manageability, and greater scalability.