October 27, 2010 at 2:15 pm
Can someone please help how to repair the node? The default instance is missing or not visible on node b. Do I need to repair the node B or Node A? if I do then how do you repair the node?
October 27, 2010 at 2:55 pm
How are you determining that node b is missing SQL Server?
Are you able to failover the 'default' instance on node A to node B?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
October 27, 2010 at 3:23 pm
Yes, I failed over to node B and I do not see the default instance. On node A we have default instance/customer database and on node b we have named instance with Reportdatabase. When I failed over to node b all I am seeing is named instance with Reportdatabase, but If I failed over to node A I can see default and named instance. How can we fix this?
October 27, 2010 at 6:58 pm
I am not clear on how you are trying to access the 'default' instance. What are you using to 'see' the instances on each node?
When you fail the 'default' instance to node b - did you verify in Cluster Administrator that all services did in fact fail over to the other node?
Remember, in a cluster - you reference the Virtual Name and not the node. As long as you are using the virtual name it doesn't matter what node is hosting the instance.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
October 27, 2010 at 8:48 pm
Ok- let's make it simple. When I login to node b (xyzdb01b) and in configuration manager/services all I can see is named instance service not MSSQLSERVER services. And when I login to node a (xyzdb01a) configuration manager/services all I can see is named instance service plus MSSQLSERVER services. ofcourse on node a the named instance are not active. This is a stage servers.
But on PRod servers on both the nodes \configuration manager/services I can see named plus default instance services.
please help-
October 27, 2010 at 10:39 pm
hydbadrose (10/27/2010)
Ok- let's make it simple. When I login to node b (xyzdb01b) and in configuration manager/services all I can see is named instance service not MSSQLSERVER services. And when I login to node a (xyzdb01a) configuration manager/services all I can see is named instance service plus MSSQLSERVER services. ofcourse on node a the named instance are not active. This is a stage servers.But on PRod servers on both the nodes \configuration manager/services I can see named plus default instance services.
please help-
Okay, that tells me that one of two things. Either the default instance on node a was not installed as a clustered instance, or it was only installed on a single node of the cluster.
When you open cluster administrator, what cluster groups are defined?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 10, 2010 at 2:21 pm
This is installed as cluster, but for some reason the node b is missing the default instance.
November 12, 2010 at 12:58 pm
hydbadrose (11/10/2010)
This is installed as cluster, but for some reason the node b is missing the default instance.
If this were true - then you would not be able to failover that instance to node b. It would mean that the instance was not installed onto every node. This could have happened by creating a single node cluster, installing SQL Server, then adding a new node. Or, this could have happened by ejecting a node from the cluster and adding it back.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 12, 2010 at 1:20 pm
To add node b to the default clustered instance go into add\remove programs on the active node and under the currently installed programs click the SQL Server 2005 entry and select "Change".
On the component selection maintenance screen under installed instances select the radio button for the clustered default instance and click "Next".
On the feature mai ntenance screen select "database engine clustered" radio button and click "Next".
At the welcome screen click "Next".
At the node pre reqs check click "Next".
On the next screen click "Maintain virtual server".
On the next screen is where you add or remove nodes to the clustered instance you have selected to maintain.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 12, 2010 at 4:35 pm
Thank you so much for your reply, but this is sql 2008 servers. will you follow the same method or through the installer?
November 12, 2010 at 4:38 pm
Thank you so much for your reply, but this is sql 2008 servers. will you follow the same method or through the installer?
November 12, 2010 at 4:55 pm
hydbadrose (11/12/2010)
but this is sql 2008 servers. will you follow the same method or through the installer?
So why have you posted in the SQL Server 2005 forum then???
No, the install routine is completely different for 2008!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply