INF: Order of Installation for SQL Server 7.0 Clustering Setup

ID: Q219264

The information in this article applies to:
  • Microsoft SQL Server, Enterprise Edition, version 7.0
  • Microsoft Windows NT Server, Enterprise Edition versions 4.0, 4.0 SP4, 4.0 SP5, 4.0 SP6, 4.0 SP6a, used with:
    • Microsoft Windows NT version 4.0 Option Pack
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server

SUMMARY

When you set up a new installation of Microsoft SQL Server 7.0 Enterprise Edition for clustering, you must install applications in a prescribed order. This article describes the procedure for installing multiple Microsoft products, including Internet Information Server (IIS), Cluster Server, SQL Server 7.0 Enterprise Edition, Microsoft Distributed Transaction Coordinator (MS DTC) 2.0, and the Windows NT 4.0 Option Pack for use in a cluster environment.

WARNING: Failure to install the applications in the order listed in this article may cause the software to fail on installation. It might also require you to reformat the disk and start the installation process over again.

For detailed information on installing SQL Server 7.0, Enterprise Edition on Microsoft Cluster Server, see the following:

http://support.microsoft.com/download/support/mslfiles/70clstr.exe

SQL Server Clustering Models

Active/Active: High-Availability Solution with Static Load Balancing - Dual Virtual SQL Server Configuration

This model provides high availability and acceptable performance when only one node is online, and it provides high performance when both nodes are online. The model also allows maximum utilization of your hardware resources.

In this model, each of the two nodes makes its own set of resources available to the network in the form of virtual servers, which can be detected and accessed by clients. The capacity for each node is chosen so that the resources on each node run at optimum performance, but so that either node can temporarily take the burden of running the resources from the other when failover occurs. Depending on the resource and server capacity specifications, all client services can remain available during failover, but performance can suffer.

Each node of the two-node cluster can support an active Microsoft SQL Server service. If a node fails, the remaining node takes ownership of the shared SCSI disks and restarts the implementation of SQL Server that has failed over. Four SQL Server licenses are required to run Symmetric Virtual Server (SVS) in an Active/Active environment.

Active/Passive: "Hot Spare" Solution with Maximum Availability - Single Virtual SQL Server Configuration

This model provides the maximum availability and performance for your resources, but it requires an investment in hardware that is not in use most of the time.

One node, called a primary node, supports all clients, while its companion node is idle. The companion node is a dedicated "hot spare", ready to be used whenever a failover occurs. If the primary node fails, the hot spare node immediately picks up all operations and continues to service clients at a rate of performance that is close or equal to that of the primary node. Exact performance depends on the capacity of the hot spare node.

SQL Server can be configured to run a single Active/Passive virtual SQL Server on a Microsoft Cluster Server (MSCS) cluster. This configuration gives applications resiliency to failure but requires only a single SQL Server. One node is used as the primary node for the Symmetric Virtual Server (SVS) and the other node is the hot-standby backup. The backup node can run the customer application or be idle, acting as insurance in case of a failure. Two SQL Server licenses are required to run SVS, even when only one SQL Server is used.

NOTE: When this document was written, Microsoft Message Queue Server (MSMQ) 1.0 Site Controllers cannot be installed using SQL Server 7.0 on a cluster. Microsoft is working on this problem and will publish the resolution to this issue as soon as it is available.

This does not affect the installation of MSMQ 1.0 Routing Servers, Independent Clients, or Dependent Clients.

There is a known problem installing an MSMQ Primary Site Controller (PSC) on a cluster. For more information, see the following article in the Microsoft Knowledge Base:
Q188685 HOWTO: Install an MSMQ PSC on Microsoft Cluster Server


MORE INFORMATION

Steps for Correct Installation

    Order of Installation using Windows NT 4.0 Enterprise Edition

    WARNING: You must install Microsoft Cluster Server (MSCS) completely on at least one node before you run Windows NT Server, Enterprise Edition simultaneously on both nodes. When using MSCS, it is critical that one node be in control of the shared SCSI bus prior to the other node coming online. Failure to do so can cause the application failover to go into an "Online Pending" state and either not ever failover to the other node or totally fail.

  1. Install Windows NT 4.0 Enterprise Edition. This product includes Windows NT 4.0 Service Pack 3.

    Service Pack 3 is required to complete the Windows 4.0 Enterprise Edition installation. Do not go directly to Service Pack 4 (or later) for Windows NT if you intend to install the Windows NT option pack. Do not install Internet Information Server (IIS) during the installation of Windows NT. By default, IIS is installed and it is recommended that you clear this option during the Windows NT install process to prevent installation.


  2. Install Microsoft Internet Explorer 4.01 or later, which can be found on the Windows NT Service Pack 4 CD, which is the second CD included with SQL 7.0, Enterprise Edition.

    WARNING: DO NO INSTALL WINDOWS Service Pack 4 at this time.


  3. Create a service account for SQL or if you already have one verify it's policies so that it has been granted the right to:
    1. Act as part of the operating system.


    2. Logon as a service.


    3. Logon locally.




  4. Next, install Microsoft Cluster Server (MSCS). Other application installation options are presented with the Windows NT 4.0, Enterprise Edition installation.

    NOTE: Do not select Microsoft Message Queue Server (MSMQ) or IIS. MSMQ 1.0 is not supported on clustered SQL Server 7.0.


  5. Install the Windows NT 4.0 Option Pack if you are using Windows NT 4.0, Enterprise Edition. MSMQ should not be selected as an optional installation choice.
    For additional information, see the following article in the Microsoft Knowledge Base:


    6. Q223258 How to Install the Windows NT Option Pack on MSCS 1.0 with SQL Server 6.5 or 7.0
    For more detail refer to the following white paper:

    How to Install Windows NT Option Pack on a Cluster

    ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/ntop.exe
  6. If the Windows NT Option Pack was not installed on Windows NT 4.0 Enterprise Edition, manually create Distributed Transaction Coordinator (DTC) Resources.


    7. Stop all services except:

    • Alerter


    • Cluster Service


    • Computer Browser


    • Event Log


    • License Logging Service


    • Messenger


    • Net Logon


    • NT LM Security Support Provider


    • Plug and Play


    • Remote Procedure Call (RPC) Locator


    • Remote Procedure Call (RPC) Service


    • Server


    • Spooler


    • TCP/IP NetBIOS Helper


    • Time Service


    • Workstation


  7. Install the Windows NT 4.0 Service Pack. When installing the service pack make sure you choose to create an uninstall directory and use the Year 2000 setup from the CD-ROM. This can be done by selecting to install from the choice in the frame on the right side of the screen that appears when the CD auto runs. It is recommended that you rename the hidden directory from $NTServicePackUninstall$ to $NTServicePackUninstall$.SP4


  8. Logon to both nodes in the cluster as the SQL Service Account you previously created.


  9. Create the cluster resources for MSDTC to use in the cluster group containing the cluster drive to be used by SQL. The MSDTC resources that are required will be a unique IP Address and Network Name.

    NOTE: These resources should not be the same ones you will be using for your clustered SQL Server. The resources must be unique.


  10. Install Microsoft SQL Server 7.0 Enterprise Edition from the CD. When installing SQL both the Program Files and Data files are installed to the cluster disk.

    For more detailed information, see:
    How to Install SQL Server 7.0, Enterprise Edition on Microsoft Cluster Server: Step by Step Instructions


  11. Install SQL Server 7.0 Service Pack 1.


  12. Cluster SQL Server 7.0, Enterprise Edition using the SQL Cluster Failover Wizard.


  13. Install the current Windows NT Service Pack.

    NOTE: Prior to installing Windows NT Service Packs, it is recommended that you verify your current Windows NT Service Pack uninstall directory has been renamed. It is recommended that you rename the hidden directory, $NTServicePackUninstall$, to $NTServicePackUninstall$.SP4 and then rename it again after installing any future Service Packs, by adding .SPx as the extension, where x is the Service Pack number. This way you have uninstall directories available, should you need them. This also prevents the directories from being accidentally overwritten.


  14. Install any additional server applications required.


Order of Installation using Windows 2000 Overview

WARNING: You must install MSCS completely on at least one node before you run Windows NT Server, Enterprise Edition simultaneously on both nodes. When using MSCS, it is critical that one node be in control of the shared SCSI bus prior to the other node coming online. Failure to do this can cause application failover to go into an "Online Pending" state and either not ever failover to the other node or totally fail.
Windows 2000 Datacenter is only supported when using a 2 node cluster. Greater than 2 nodes is not supported and use of the cluster wizard will result in a failed installation.
  1. Install Windows 2000 Advanced Server RC3 or later, accepting the default application choices. Windows 2000 is en route to computer manufacturers and stores, in time for a worldwide launch on February 17, 2000


  2. After installing Windows 2000 on the first node (and prior to installing MSCS), from the Start menu, point to Programs, point to Administrative Tools and then select Configure Your Server.


  3. In the dialog box, select Choose Advanced\Cluster Service, and from the right side, choose Learn More.


  4. Review item 2 under Windows Clustering. This is the type of clustering you will be setting up and installing for SQL Server 7.0, Enterprise Edition to use. IMPORTANT: It is necessary to read the section on "Planning for Windows Clustering\Requirements" for server clusters and to follow the Checklist for server clusters named "Checklist: Creating a server cluster". This is found under the "Server Clusters" section and "Checklist" for server clusters.


  5. Create a service account for SQL. If you already have one verify it’s policies so that it has:

    1. Right to act as part of the operating system.


    2. Logon as a service.


    3. Logon locally.


    NOTE: This requires a Domain Administrators account to set up the domain policy. For assistance, refer to "Windows 2000 Group Policy Scenarios" at:
    http://www.microsoft.com/windows/server/Technical/management/GroupPolicyIntro.asp
    -or-
    http://www.microsoft.com/windows/server/Technical/management/grouppolicy.asp


  6. Stop all services except:


    • Alerter


    • Cluster Service


    • Computer Browser


    • Distributed File System


    • Distributed Link Tracking Client


    • Distributed Link Tracking Server


    • DNS Client


    • Event Log


    • IPSEC Policy Agent


    • License Logging Service


    • Logical Disk Manager


    • Messenger


    • Net Logon


    • NT LM Security Support Provider


    • Network Connectors


    • Plug and Play


    • Process Control


    • Remote Procedure Call (RPC) Locator


    • Remote Procedure Call (RPC) Service


    • Remote Registry Service


    • Removable Storage


    • Security Accounts Manager


    • Server


    • Spooler


    • TCP/IP NetBIOS Helper


    • Windows Management Instrumentation Driver Extensions


    • Windows Time Service


    • Workstation


  7. Install Microsoft SQL Server 7.0 Enterprise Edition from the compact disk. When installing SQL both the Program Files and Data files are installed to the cluster disk.


  8. Install SQL Server 7.0 Service Pack 1.


  9. Verify only the minimum services are started as previously listed. One additional thing may now be started, check your systray for the SQL Service Manager, if found right click on it and choose Exit.


    10. NOTE: Microsoft has confirmed this to be a problem in Microsoft Windows 2000.
  10. Cluster SQL Server 7.0, Enterprise Edition using the SQL Cluster Failover Wizard.

    IMPORTANT: After you have successfully clustered SQL, you will need to make Distributed Transaction Coordinator (DTC) cluster aware (if it is not already).


  11. From the Start menu, point to Programs, point to Administrative Tools and select Cluster Administrator. In the dialog box, select View Groups\Cluster Group. If the group contains a MSDTC resource then MSDTC is already clustered. If not, complete the following two steps.


  12. From the Start menu, point to Run and enter Comclust.exe in the dialog box. Click OK.


  13. Repeat the previous step on the remaining node.

    NOTE: If Comclust.exe runs prior to installing SQL, the Clustered DTC resource will be created in the Cluster group or the first group it finds containing the following three resources:

    • IP Address


    • Network Name


    • Cluster Disk




  14. Install any additional server products before installing any user applications.


Clear the System Event Logs in both nodes, restart the nodes, and view the System Event Logs again. Please resolve any errors before proceeding further.

Additional query words: Installation Order MSCS SQL 7.0 Datacenter Windows 2000

Keywords : kbinterop kbsetup SSrvInst kbNTOS400 kbWinOS2000 kbSQLServ700
Version : WINDOWS:2000; winnt:4.0,4.0 SP4,4.0 SP5,4.0 SP6,4.0 SP6a,7.0
Platform : WINDOWS winnt
Issue type : kbinfo


Last Reviewed: December 23, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.