July 28, 2002 at 11:59 am
If anyone has any suggestion, please let me know.
Books online has steps for upgrading from a default instance of SQL Server to a default Cluster installation and When I follow the instructions (I pretty sure I am doing everything exactly as documented), The "Upgrade your existing installation to a clustered installation" option is grayed out ont he "Existing Installation" Screen. The only option I have now is to unistall and re-install SQL Server in clustered mode. This means I will loose existing registry entries, etc.
July 29, 2002 at 10:13 am
I am using enterprise version. The standalone version that I installed first is the Enterprise Edition of SQL Server on Windows Advanced server. I am running the latest patches on both. I was able to cluster SQL Server when I uninstall and reinstall.
July 29, 2002 at 10:16 am
The answer to your question is - The default instance is Enterprise edition.
July 29, 2002 at 11:11 am
SQL Server 2000 Enterprise version. Sorry, I should have stated this. I have the cluster service etc. installed properly. MSDTC is already working under the cluster service. I used COMClust.exe to run MSDTC under cluster service.
Thanks,
Krishna
July 30, 2002 at 3:04 pm
quote:
I don't have a SQL Server environment that I am supporting, but have read a number of documents on this topic. Therefore must apologize in advance if my advice is not the best.First, let me draw the conclusion that if you are encountering a greyed out section during the upgrade, this means that the process has detected something that makes it determine this option is not to be available.
I believe the correct process to get to a clustered environment is to get the Windows clustered environment established first.
Has this been done?
Then of course we would follow with trying to get the SQL Server 2000 clustered environmnet established.
BOL has the following topic: How to upgrade from a default instance to a default clustered instance of SQL Server 2000 (Setup)
Am I correct in assuming that SQL Server is running as the "default" instance and not a named instance?
Am I correct in assuming that you are trying to do a local install and not a remote install?
Now I'll try steping through the install process.
On the Welcome screen of the SQL Server Installation Wizard, click Next.
On the Computer Name screen, click Local Computer. The computer you want to change from a default to a clustered instance should be displayed. You must be on the local computer to upgrade from a default to a clustered instance. Click Next.
On the Installation Selection screen, click Upgrade, remove, or add components to an existing instance of SQL Server. Click Next.
What did you select at this point? Upgrade, remove, or add components?
On the Existing Installation screen, click Upgrade your existing installation to a clustered installation. Click Next.
The above I believe is what you are telling me is greyed out. Correct?
On the Virtual Server Name screen, enter a name for your virtual server. Click Next.
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 Microsoft Cluster Service (MSCS). Continue to enter IP addresses for each installed network until you have populated all desired networks with an IP address. Click Next.
On the Cluster Management screen, review the failover cluster definition provided by SQL Server 2000. By default, all available nodes are selected. Remove any nodes that will not be part of the failover cluster definition for the virtual server you are creating. Click Next.
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.
On the Services Accounts screen, select the service account(s) for the SQL Server services under which you want the failover cluster to run. Click Next.
On the Setup Complete screen, click Finish. If you need to restart the remote nodes in the failover cluster, you will be instructed to do so in the Setup Complete screen.
Will get back to you after you have had a change to answer these questions.
solart
July 30, 2002 at 3:07 pm
My answers are below. Thank you for the help.
quote:
I don't have a SQL Server environment that I am supporting, but have read a number of documents on this topic. Therefore must apologize in advance if my advice is not the best.First, let me draw the conclusion that if you are encountering a greyed out section during the upgrade, this means that the process has detected something that makes it determine this option is not to be available.
I believe the correct process to get to a clustered environment is to get the Windows clustered environment established first.
Has this been done? yes
Then of course we would follow with trying to get the SQL Server 2000 clustered environmnet established.
BOL has the following topic: How to upgrade from a default instance to a default clustered instance of SQL Server 2000 (Setup)
Am I correct in assuming that SQL Server is running as the "default" instance and not a named instance? yes
Am I correct in assuming that you are trying to do a local install and not a remote install? yes
Now I'll try steping through the install process.
On the Welcome screen of the SQL Server Installation Wizard, click Next.
On the Computer Name screen, click Local Computer. The computer you want to change from a default to a clustered instance should be displayed. You must be on the local computer to upgrade from a default to a clustered instance. Click Next.
On the Installation Selection screen, click Upgrade, remove, or add components to an existing instance of SQL Server. Click Next.
What did you select at this point? Upgrade, remove, or add components? yes
On the Existing Installation screen, click Upgrade your existing installation to a clustered installation. Click Next.
The above I believe is what you are telling me is greyed out. Correct? yes. This option was greyed out. I did not proceed any further.
On the Virtual Server Name screen, enter a name for your virtual server. Click Next.
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 Microsoft Cluster Service (MSCS). Continue to enter IP addresses for each installed network until you have populated all desired networks with an IP address. Click Next.
On the Cluster Management screen, review the failover cluster definition provided by SQL Server 2000. By default, all available nodes are selected. Remove any nodes that will not be part of the failover cluster definition for the virtual server you are creating. Click Next.
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.
On the Services Accounts screen, select the service account(s) for the SQL Server services under which you want the failover cluster to run. Click Next.
On the Setup Complete screen, click Finish. If you need to restart the remote nodes in the failover cluster, you will be instructed to do so in the Setup Complete screen.
Will get back to you after you have had a change to answer these questions.
solart
July 30, 2002 at 7:42 pm
My Answer is below -
Would I be correct in assuming that in creating the Windows clustered environment that a quorum disk and a "clustered" disk have been added to the hardware environment?
yes
July 30, 2002 at 7:43 pm
My answer is below -
When comclust.exe was ran, was MSDTC assigned to the quorum disk?
yes
July 30, 2002 at 10:25 pm
The whole problem is occuring because I have a default instance of SQL Server 2000 installed on the second node in the cluster as well. When I remove the SQL Server installation from the second node, the required option becomes available when I run the setup on the first node. It does not solve my problems entirely but at least I know now the cause is for the observed behavior.
Thaksm you for your help.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply