SQL2k8 -> SQL2k8 R2 Upgrade

  • I'm upgrading SQL2k8 to SQL2k8 R2 in a 2-node cluster. The servers are running W2k8 Ent.

    I followed the information in Microsft's guide

    http://msdn.microsoft.com/en-us/library/ms191295.aspx

    I've upgraded the passive node to R2, but I'm unable to move SQL to this node. I'm getting the following error when I try.

    The action 'Move to node <NodeB>' did not complete. An error occurred moving the clustered service or application 'SQL Server (<InstanceName>)'. the operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.

    I think the problem is a resource in Failover Clustering, but not real sure & I'm lost @ this point.

    One of the items in the Next Steps from the article is Register your Servers. What does this mean & is it germain to my issue?

    Any advice will be appreciated.

  • In Cluster Manager, is NodeB in the Possible Owners List if your Cluster Group?



    Ole Kristian Velstadbråten Bangås - Virinco - Facebook - Twitter

    Concatenating Row Values in Transact-SQL[/url]

  • You need to check whether you assigned one of the clustered resources to the 2nd node.

    -Satya SK Jayanty
    SQL Server MVP (Follow me @sqlmaster)
    Author of SQL Server 2008 R2 Administration CookBook
    SQL Server Knowledge Sharing network

  • BigSam (8/31/2011)


    I'm upgrading SQL2k8 to SQL2k8 R2 in a 2-node cluster. The servers are running W2k8 Ent.

    I followed the information in Microsft's guide

    http://msdn.microsoft.com/en-us/library/ms191295.aspx

    I've upgraded the passive node to R2, but I'm unable to move SQL to this node. I'm getting the following error when I try.

    The action 'Move to node <NodeB>' did not complete. An error occurred moving the clustered service or application 'SQL Server (<InstanceName>)'. the operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.

    I think the problem is a resource in Failover Clustering, but not real sure & I'm lost @ this point.

    One of the items in the Next Steps from the article is Register your Servers. What does this mean & is it germain to my issue?

    Any advice will be appreciated.

    Open up failover cluster manager and for the sql server instance group open the properties and check the preferred owners to see whether the node is listed. Also open the properties for the clustered sql server service and check the possible owners, is the node listed there?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • I opened Failover Cluster Manager, expanded my cluster - there are 4 points to further expand: Services & Applications, Nodes, Storage & Networks.

    In Services & Applications, right-click SQL Server & select properties. Both servers are checked as preferred owners.

    In Nodes, both servers are listed.

    In Storage I see all the disk volumes. The Witness is on NodeA (upgraded), the Data & Logs are on NodeB.

    In Networks all of my connections are up.

    When you say 'Open up failover cluster manager and for the sql server instance group open', do you mean the cluster I created for SQL? Is 'yes', then the only way to view the preferred owners is by selecting 'Manage Core Cluster Resource Group' from the General tab. In the Cluster Group, none of the nodes are checked as preferred owners. However, checking or unchecking these has no impact on my ability to move the service to the upgraded node; I get the same error.

    When I expand SQL Server in the Services & Applications I do not see the Witness disk. Could that be the problem?

    Thanks for the help & sorry for being so ignorant on this topic.

  • BigSam (9/1/2011)


    I opened Failover Cluster Manager, expanded my cluster - there are 4 points to further expand: Services & Applications, Nodes, Storage & Networks.

    In Services & Applications, right-click SQL Server & select properties. Both servers are checked as preferred owners.

    In Nodes, both servers are listed.

    inside this sql server group will be a set of resources (disk, ip,etc). Right click the sql server and its agent resource and check the possible owners list

    BigSam (9/1/2011)


    The Witness is on NodeA (upgraded)

    when you say witness i'm assuming youre referring to the quorum drive. What quorum model are you using disk only or disk and node majority?

    Can you provide exact details of the steps YOU took to complete the rolling upgrade?

    Also check the cluster event log and the windows application log for more details and post them back

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • I found the problem.

    I thought I upgraded the passive node, falied over to it & then upgraded the other server.

    After upgrading the passive node, then the Active node I was able to get everything working.

    Thanks for your interest, time & advice.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply