Setting up Always On Availability Groups with Windows Server Failover Cluster
-
I'm trying to setup Always On for SQL Server with two nodes.
I have two SQL Servers in two different co locations.
I ran through the failover cluster validation and everything looked good except that it complained about each node only having 1 pair of network interfaces.
I next ran through the wizard to create a cluster and now get the following errors.
"This resource is marked with a state of 'Offline'. The functionality that this resource provides is not available while it is in the offline state. The resource may be put in this state by an administrator or program. It may also be a newly created resource which has not been put in the online state or the resource may be dependent on a resource that is not online. Resources can be brought online by choosing the 'Bring this resource online' action in Failover Cluster Manager."
I go to Failover Cluster Manager to try to bring it online and then get the following message.
"The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource"
Any suggestions of what I need to do to bring this second node online so I can continue with configuring Always ON?
-
Hi,
Don't right click and bring it online.
Instead, on the right hand side you have an option to
More Actions ==> Move More Cluster Resources ==> Select Node
Once you failover, automatically the other IP would come online.Me not sure if I got your question right though.
In cluster only one cluster IP would be online anyway, you can go ahead and configure AG in SQL Server. - Joy Smith San - Wednesday, September 12, 2018 8:34 PM
When I click on More Actions, there are 3 options.
Simulate Failure and Assign to Another Node, both of which are greyed out.
The third option is Show Dependency Report which brings up a Dependency Report .htm page in Internet Explorer.I wonder if it is some sort of permissions issue or something else possibly.
Do you have any other suggestions?
Thanks,
-
What is windows version ?
Are you a local admin on the server ?Mine is Windows 16.
I get "More Actions" in 2 places on the right hand under "Actions" tab.
First "More Actions" is under cluster's FQDN with domain name in it.
That's where I get to see these options.Can post screenshot ?.
Bye the way, is the cluster up n running ?. If yes, what stops you from configuring AG ?.
You failover/back on AG from SQL Server end.
Of course windows cluster issues need to be sorted out, which is different issue.
however as long as the cluster is up running you should be able to add AG.Thanks !.
-
I am running Windows Server 2016 Standard and SQL Server 2016 Enterprise
I was not an admin on the windows server before but have just added myself now to both windows servers (primary and secondary)
The cluster appears to be up and I was playing around with setting up AG now in SQL Server which appears to be working ok initially, but the following does not look correct in Failover Cluster Manager See attached screenshot.
The concerns I have are the red X in the top left-hand corner (let me know if for some reason this screenshot is too small) and also at the very bottom under Cluster Core Resources.
The first IP address which ends in 88.68 which is my secondary DR SQL Server is offline and when I try to bring the second IP offline (1.68) and then bring 1.88 online I get the following error messageAlso under Cluster Events, I see the following error.
Cluster resource 'Cluster IP Address xx.xx.88.68' of type 'IP Address' in clustered role 'Cluster Group' failed.Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
I also see the following warnings in the Failover Cluster Validation Report.
Let me know if I can provide any additional details.
-
Hi,
Again, I am not a windows expert.
However it looks OK to me in fact.1. The red X in the top left-hand corner
That should be because some errors have already been logged, not necessarily that still exists or still a concern.2. The first IP address which ends in 88.68 which is my secondary DR SQL Server is offline and when I try to bring the second IP offline (1.68) and then bring1.88 online I get the following error message
This too is expected (to my knowledge) as you are trying to bring a cluster IP online directly from a PASSIVE node. What I was telling earlier was, we don't need to bring this IPs ONLE/OFFLINE by ourselves. When the fail over happens cluster manager might bring it online/offline automatically
Ensure you are local admin on both the nodes. And login to ACTIVE node. Just select Cluster name and see if you get to see the option at right hand side.
More Actions ==> Move More Cluster Resources ==> Select Node
(As stated earlier, I get "More Actions" in 2 places at the right hand under "Actions" tab. First "More Actions" is under cluster's FQDN with domain name in it. That's where I get to see these options.)
If you are able to do this, and the node/IP doesn't come online, then there is a problem with that IP. You might need to check with windows guys.3. Otherwise AG is OK ?. Everything working fine ?
I just pinged whatever I know. Think other experts here might be able to help you on this cluster part.
- Joy Smith San - Wednesday, September 12, 2018 8:34 PM
This looks like an FCI, not an AG setup?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply