August 18, 2015 at 7:14 am
We have a SQL 2014 AlwaysOn availability group running on two Windows 2012 R2 servers that are in the same subnet. We created a new server in a second subnet, installed SQL, joined the server to the Windows cluster, added a new IP resource for the new cluster, and performed the other remaining steps to add a new AG replica to the SQL instance on this new server. When we try to move the core cluster resources to the new node to test failover, we get an error. Here's the command we've been using:
Move-ClusterGroup "Cluster Group" -Node node3
and it returns the error:
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've checked the ownership of the cluster groups and the cluster resources and it looks like they are set appropriately:
>Get-ClusterGroup | Get-ClusterOwnerNode
Cluster Object Owner Nodes
---------------- ---------------
Available Storage {}
Cluster Group {node1,node2,node3}
SQLAG {node1,node2,node3}
>Get-ClusterResource | Get-ClusterOwnerNode
Cluster Object Owner Nodes
---------------- ---------------
Cluster IP Address 1 {node1,node2}
Cluster IP Address 2 {node3}
Cluster Name {node1,node2,node3}
SQLAG {node1,node2,node3}
SQLAG IP 1 {node1,node2}
SQLAG IP 2 {node1,node2}
SQLAG Listener {node1,node2,node3}
We've double-checked that all IP resources are in the right subnets and that the dependencies for the Cluster Name resource and the Listener Name resource are set appropriately. I'm not sure what else to check since the PowerShell commands seem to indicate that node3 is an owner of the appropriate resources. Does anyone know what other things need to be checked or if the ownership being checked isn't the same as what PowerShell is checking?
August 18, 2015 at 10:14 am
can you provide a resource dependency report please using the following
get-clusterresourcedependencyreport -group YourAG_Name | copy-item -destination drive:\somefolder
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 18, 2015 at 10:26 am
Thank you for replying!
The dependency report says:
'SQLAG Name' dependencies are 'Name: SQLAG Listener Name'
'SQLAG Name' has no required dependencies
'SQLAG Listener IP 1' has no required dependencies
'SQLAG Listener IP 2' has no required dependencies
'Name: SQLAG Listener Name' dependencies are 'SQLAG Listener IP 1' or 'SQLAG Listener IP 2'
'SQLAG Listener Resource Name' required dependencies are IP Address.
Let me know if you need more info that this.
August 18, 2015 at 4:45 pm
We ended up rebuilding the clusters with all three nodes from scratch since including all nodes at the beginning doesn't seem to hit the same issues. I'm not sure what the initial problem was with adding a node, but it's now moot.
Thank you for replying Perry! If you have a theory and still want to post it, feel free.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply