Export (0) Print
Expand All

Maintaining a Failover Cluster (64-bit)

SQL Server 2000

  This topic applies only to SQL Server 2000 (64-bit).

After you have installed a Microsoft® SQL Server™ 2000 (64-bit) failover cluster, you can change or repair your existing setup. For example, you can add additional nodes to a virtual server in a failover cluster, run a clustered instance as a stand-alone instance, remove a node from a clustered instance, or recover from failover cluster failure.

Adding a Node to an Existing Virtual Server

During SQL Server Setup, you are given the option of maintaining an existing virtual server. If you choose this option, you can add other nodes to your failover cluster configuration at a later time. You can add up to three additional nodes to an existing virtual server configured to run on one node.

To add a node to an existing virtual server

SQL Setup

Removing a Node from an Existing Failover Cluster

You can remove a node from a virtual server (for example, if a node is damaged). Each node in a virtual SQL Server is considered a peer, and you can remove any node.

A removed node can be added back to a failover cluster at any time. For example, a removed node can be rebuilt after a failure and added back to the failover cluster. Alternatively, if a node is temporarily unavailable and later comes back online, and an instance of SQL Server 2000 (64-bit) from the affected virtual server is still in place, the Setup program removes this instance from the computer before installing the binaries on the node again.

Note  A damaged node does not have to be available to be removed, but the removal process will not uninstall any of the binaries from the unavailable node.

To remove a node from an existing failover cluster

SQL Setup

Running a Clustered Instance of SQL Server as a Stand-Alone Instance

Usually, you run a clustered instance of SQL Server under the control of Microsoft Cluster Service (MSCS). However, it may be necessary to run a clustered instance of SQL Server as a stand-alone instance (for example, when you want to perform administrative operations like running an instance of SQL Server in single-user mode). To connect to a clustered instance of SQL Server 2000 in stand-alone mode using sockets, both the IP address and network name resources must be online for the virtual server on which the instance was installed.

If these resources cannot be online, connect using Named Pipes. However, you must create an alias on the client side to talk to the pipe name on which the instance of SQL Server is listening. Use SQL Server Network Utility to find out the pipe name. For more information, see the "SQL Server Network Utility" topic in the SQL Server 2000 32-bit Books Online. For more information, see Failover Cluster Troubleshooting (64-bit).

Recovering from Failover Cluster Failure

Usually, failover cluster failure is due to one of these causes:

  • Hardware failure in Node 1 of a two-node cluster. This hardware failure could be caused by a failure in the SCSI card or the operating system.

    To recover from this failure, first remove the failover cluster using the Setup program.

To remove a failover clustered instance

SQL Setup

To recover from failover cluster failure in Scenario 1

SQL Setup

  • Node 1 is down or offline, but not irretrievably broken. This could be caused by an operating system failure. However, recovering from operating system failure using the steps below can take time. If the operating system failure can be recovered easily, avoid using this technique.

    To recover from this failure, first remove the failover cluster using the Setup program.

To remove a failover clustered instance

SQL Setup

To recover from failover cluster failure in Scenario 2

SQL Setup

Changing Service Accounts

You should not change the passwords for any of the SQL Server service accounts when a failover cluster node is down or offline. If you have to do this, you will need to reset the password again using SQL Server Enterprise Manager when all nodes are back online. To use SQL Server Enterprise Manager on your SQL Server 2000 (64-bit) installations, you must administer the tool remotely from a 32-bit computer.

If the service account for SQL Server is not an administrator in a cluster, the administrative shares cannot be deleted on any nodes of the cluster. The administrative shares must be available in a cluster for SQL Server to function.

Do not use the same account for the SQL Server service account and the Cluster service account. If the password changes for the Cluster service account, your SQL Server installation will fail.

See Also

Handling a Failover Cluster Installation (64-bit)

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft