December 11, 2014 at 8:31 am
I am able to successfully configure windows cluster on windows server 2008 R2,I would like to know before doing sql clustering on it.
When I install Sql on node1 which is on cluster,as normal step for installation ,I require to restart my vm machine(i.e Node1) after installing Sql server 2012 ent edition.
Now in that case my windows cluster would failover,then What should I do to resolve this problem.
Do I need to stop windows cluster while installing Sql on clustered node?
Please if anybody can throw light on this...what I am missing here???
December 11, 2014 at 8:41 am
sej2008 (12/11/2014)
I require to restart my vm machine(i.e Node1) after installing Sql server 2012 ent edition.Now in that case my windows cluster would failover,
If node1 was the only node the instance is installed to, i.e. you havent installed to node 2 yet, then no it wont failover as it cannot run on node 2. The group will just stay offline
sej2008 (12/11/2014)
then What should I do to resolve this problem.Do I need to stop windows cluster while installing Sql on clustered node?
Please if anybody can throw light on this...what I am missing here???
Dont need to do anything at this point. Reboot the node and when it comes back up ensure the group comes back online
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 11, 2014 at 11:12 am
ok,fine I was talking about windows cluster group that failed in my case and it showed critical events on Node1 in FCM with NODE and Disk Majority warning....
I failed to understand this...
what is wrong here??
December 11, 2014 at 11:15 am
can you post some of the errors
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 12, 2014 at 3:47 am
ok I will do that...
December 12, 2014 at 4:20 am
I got in cluster events the following message....
Node 'Node1' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
Another Cluster Events message were as following.....
Cluster node 'Node2' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Another error............
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
December 12, 2014 at 4:32 am
Also I am getting Red cross small icon on my cluster in Failover Cluster manager summary page.
I am doing the setup for High Availibility Group understanding with out SAN as you do not need any shared storage as per my
understanding......
December 12, 2014 at 4:40 am
so, if i'm reading corect now you're not deploying a failover cluster instance of sql server you're deploying standalone instances and intend to use AlwaysOn availability groups, is that correct?
Can you detail exactly what you have installed so far and how you did it?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 12, 2014 at 9:16 pm
ok
December 17, 2014 at 10:58 am
I am learning both sql clustering and also Always on and both
require wCF but not able to get success in windows clustering so far...
As I am getting error of cluster Disk all the time I continue to do practical on HAG but that is also not working again replica nodes are not getting connected as I am trying to configure through HAG wizard though I am working as a Administrator...am I missing AD security related setps???
December 18, 2014 at 5:04 am
what is it you are trying to achieve?
Are you trying to setup a clustered instance of sql server or an alwayson availability group?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply