November 8, 2013 at 2:55 pm
I am setting up two test servers loaded with SQL Server2012 Enterprise edition, one in a datacenter on the East Coast and one server in a datacenter on the West Coast. As I understand it and I have configured both serves to turn on Filover clusterig. When I stepped thru the process on the first server (Primary server) when I got to the dialog screen that asked for "Select Servers or a Cluster" I am not sure if I am to enter just the server I am working on or to enter both servers (one on the east coast and one on the west coast) that will make up a named cluster.
On the next screen it ask to name the cluster which I did and then it list the two networks the servers are on and ask for an IP.I am not sure if I should just pick the first available IP address that is not used or be concerned that the network admins need to be consulted. I went ahead and ran thru all the steps and the process completed OK. I logged into what I hope to be my standby machine and tried to see if it recognized the cluster I set up on the primary server and it came back with an error.
So I guess what I a asking is if I just want to set up two remote servers so that if one fails the other server will come online am I talking about one node server cluster or am I talking about a two node server failover cluster and should I be able to see the named cluster from both modes when configuring/managing:unsure:
November 11, 2013 at 8:10 am
Reg_Mayfield (11/8/2013)
When I stepped thru the process on the first server (Primary server) when I got to the dialog screen that asked for "Select Servers or a Cluster" I am not sure if I am to enter just the server I am working on or to enter both servers (one on the east coast and one on the west coast) that will make up a named cluster.
When creating the Windows cluster you need to select all nodes that will be a part of the cluster.
Reg_Mayfield (11/8/2013)
On the next screen it ask to name the cluster which I did and then it list the two networks the servers are on and ask for an IP.I am not sure if I should just pick the first available IP address that is not used or be concerned that the network admins need to be consulted. I went ahead and ran thru all the steps and the process completed OK. I logged into what I hope to be my standby machine and tried to see if it recognized the cluster I set up on the primary server and it came back with an error.
You need to consult your sys admins to ensure the cluster virtual IP and network name fit with their standard and are not in use
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 15, 2013 at 2:08 pm
I have been at this for several days and have been able to complete the windows cluster. I have created an availability group with my two nodes. I have three databases that I have included as part of the AG. I have two Replicas one Primary and one Secondary. I went thru the AG setup and everythin passed. But once I tried to join the databases to the AG I got the error :
The connection to the primary replica is not active. The command cannot be processed. (Micorsoft Sql Server , error:35250) I have Googled tis error but no luck in finding out what the actual issue is and how to correct???
Anyone have an idea ( I feel like am so close)
November 15, 2013 at 2:37 pm
You may to check network connectivity issues. Perhaps the default port is hung from one of your prior problems. Check for any routing/firewall issues. Good luck.
November 15, 2013 at 2:43 pm
Thanks...
I checked the both servers and sure nuff the secondary server had its firwall enabled whereas the primary server had its firewall disabled. I disabled the firewall on the secondary server then joined the databases to the AG and everything is now working as advertized...
Thanks for pointing me in the right direction:hehe:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply