How to create a new failover cluster (Setup)

SQL Server Setup Help

SQL Server Setup Help

How to create a new failover cluster (Setup)

Important  Before you create a Microsoft® SQL Server™ 2000 failover cluster, you must configure Microsoft Cluster Service (MSCS) and use Cluster Administrator in Microsoft Windows NT® 4.0 or Windows® 2000 to create at least one cluster disk resource. Note the location of the cluster drive in the Cluster Administrator before you run SQL Server Setup because you need this information to create a new failover cluster.

To create a new failover cluster

  1. On the Welcome screen of the Microsoft SQL Server Installation Wizard, click Next.

  2. On the Computer Name screen, click Virtual Server and enter a virtual server name. If Setup detects that you are running MSCS, it will default to Virtual Server. Click Next.

  3. On the User Information screen, enter the user name and company. Click Next.

  4. On the Software License Agreement screen, click Yes.

  5. On the Failover Clustering screen, enter one IP address for each network configured for client access. That is, enter one IP address for each network on which the virtual server will be available to clients on a public (or mixed) network. Select the network for which you want to enter an IP address, and then enter the IP address. Click Add.

    The IP address and the subnet are displayed. The subnet is supplied by MSCS. Continue to enter IP addresses for each installed network until you have populated all desired networks with an IP address. Click Next.

  6. On the Cluster Disk Selection screen, select the cluster disk group where the data files will be placed by default. Click Next.

  7. On the Cluster Management screen, review the cluster definition provided by SQL Server 2000. By default, all available nodes are selected. Remove any nodes that will not be part of the cluster definition for the virtual server you are creating. Click Next.

  8. On the Remote Information screen, enter login credentials for the remote cluster node. The login credentials must have administrator privileges on the remote node(s) of the cluster. Click Next.

  9. On the Instance Name screen, choose a default instance or specify a named instance. To specify a named instance, clear the Default check box, and then enter the name for the named instance. Click Next.

    Important  You cannot name an instance DEFAULT or MSSQLSERVER. For more information about naming instances of SQL Server 2000, see Working with Named and Multiple Instances of SQL Server 2000. Names must follow rules for SQL Server identifiers. For more information about naming conventions for identifiers, see Using Identifiers.

  10. On the Setup Type screen, select the type of installation to install. The Setup program automatically defaults to the first available cluster disk resource from the group you previously selected.

    However, if you need to specify a different clustered drive resource, under Data Files, click Browse and then specify a path on a clustered drive resource. You will be required to select a clustered drive resource that is owned by the node on which you are running the Setup program. The drive also must be a member of the cluster group you previously selected. Click Next.

  11. On the Services Accounts screen, select the service account(s) that you want to run in the failover cluster. Click Next.

  12. In the Authentication Mode dialog box, choose the authentication mode to use. If you change the selection from Windows Authentication Mode to Mixed Mode (Windows Authentication and SQL Server Authentication), you need to enter and confirm a password for the sa login.

  13. On the Start Copying Files screen, click Next.

  14. On the Setup Complete screen, click Finish.

    If you are instructed to restart the computer, do so now. It is important to read the message from the Setup program when you are done with installation. Failure to restart any of the specified nodes may cause failures when you run the Setup program in the future on any node in the failover cluster.