August 4, 2016 at 10:05 pm
I have a 2 node cluster and were supposed to run the upgrade advisor against passive node first, but how can you when the passive node sql service is not running? When I run the upgrade advisor I get the below error. Appreciate the help.
Unable to connect to server. Reason: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
August 5, 2016 at 6:45 am
I would think you could only run the upgrade advisor on the active node only. The advisor checks for database issues that would arise if the upgrade occurs. Where did you read that it must be run on the inactive node?
August 5, 2016 at 10:13 am
I didn't read it I just assumed that since we have to upgrade the passive node first you would need to run the upgrade advisor against the node your upgrading right?
August 5, 2016 at 11:05 am
The advisor appears to examine all sql components. I was thinking it was just centered at the instance level only. If your cluster has different non-clustered aware components (rare) on different nodes, like Reporting Services or Analysis Services, you could run it against them also. The thing is you have to be able to connect to the instance or component for the utility to function:
On the SQL Server Components page, enter the name of the server to scan in the Server name box, and then click Detect. Use the following guidelines for the server name:
?To scan non-clustered instances, enter the computer name.
?To scan clustered instances, enter the virtual SQL Server name.
?To scan non-clustered components that are installed on a node of a cluster, enter the node name.
If my thinking is correct, you can only connect to an active instance or component, so, in your case, you will only ever be able to run it against the active node whichever one applies.
August 5, 2016 at 11:09 am
Ok sounds good. I'm assuming though you don't need the sql services running on the passive node to run the sql upgrade correct? Sorry this is my first time doing this and it's against PROD. Appreciate the help.
August 5, 2016 at 11:19 am
Correct, you will always want to run an upgrade on the passive node first. Then, when you failover the instance back to that first upgraded node, the databases get automatically upgraded. Upgrades are making modifications to system tables, etc. at the instance level which is why the databases do not have to be "active" for an upgrade to run.
August 5, 2016 at 12:55 pm
In your Failover cluster manager, do you have both nodes Up? In the Roles, you see which one is the active.
Both nodes should be up; the services for the passive are offline of course.
What you need is to run the upgrade and start the process. After that you'll simply failover from the active to the passive node and repeat the upgrade on the other node (which services go offline after the failover).
I've been doing it many times, it's simple.
Igor Micev,My blog: www.igormicev.com
August 8, 2016 at 10:12 am
Yes both nodes are up. Thanks guys appreciate the information!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply