SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Combining AlwaysOn Groups With Failover Cluster Instances


Combining AlwaysOn Groups With Failover Cluster Instances

Author
Message
colin Robinson-345240
colin Robinson-345240
SSC-Enthusiastic
SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)SSC-Enthusiastic (125 reputation)

Group: General Forum Members
Points: 125 Visits: 148
Perry,

Your article suggested you could make the single Listener HA, Could you explain how this is achieved please ?
Hikmer
Hikmer
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 59
Thanks fro this article, but you don't actually say HOW to do this...I want to setup an AO group for an existing failover cluster and it isn't clear which wizard or settings to use (do I specify the nodes or VIP or something else when setting up the cluster and replicas?) Documentation on this is very sparse.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53689 Visits: 17672
Hikmer (1/27/2014)
Thanks fro this article, but you don't actually say HOW to do this...I want to setup an AO group for an existing failover cluster and it isn't clear which wizard or settings to use (do I specify the nodes or VIP or something else when setting up the cluster and replicas?) Documentation on this is very sparse.

Thats because this is not a deployment guide! Thats a whole separate article. Deploying an AO group is no different when using an FCI replica you just need to be aware of the increased complexity. This guide shows the typical wizard options when creating the AO group.

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

"Ya can't make an omelette without breaking just a few eggs" ;-)
Hikmer
Hikmer
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 59
Thanks, yes I have deployed an AlwaysOn Availability group and these instruction are straight forward...what I am lacking is a guide to combine Fail-over Clustering with AlwaysOn Availability. I have two 2 node failover cluster environments (SQL 012 with shared disks, etc.) and want to create an Availability group between them for added redundancy and DR....however I cannot figure out how to do it..or even if it is possible. People alluded that is it online but I have yet to find this mystical guide. One article combines two different technologies...the other walk through leaves Failover Clustering out completely...or am I wrong?

PS You also don't mention how to create the secondary database to Join in the Always On Wizard, and while trivial to some, it was a step I had some issues as I needed to leave it in a recovering sate. Not trying to be a jerk...just struggling with this as Microsoft doesn't seem to have an good articles on this subject matter.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53689 Visits: 17672
Hikmer (1/27/2014)
what I am lacking is a guide to combine Fail-over Clustering with AlwaysOn Availability.

I have a guide being published soon on SSC showing how to achieve this, starting from scratch.


Hikmer (1/27/2014)
I have two 2 node failover cluster environments (SQL 012 with shared disks, etc.) and want to create an Availability group between them for added redundancy and DR....however I cannot figure out how to do it..or even if it is possible.

All nodes that have an instance, clustered or non clustered, that is to participate in an AO group must be part of the same windows cluster. What you are attempting is possible but only for migration purposes, it is not a supported permanent solution, as objects (like the listener) cannot move between clusters.

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

"Ya can't make an omelette without breaking just a few eggs" ;-)
pamozer
pamozer
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1855 Visits: 443
I have a question about storage. I have a 3 node windows cluster. 2 FCIs on san storage and 1 node on a separate san. For Always On you need to have the same lettered drives correct? And you should be able to do that with a Windows Cluster? My storage guy is telling me they can't be the same drive letters if they are in the same windows cluster.
david.puckett 38841
david.puckett 38841
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 0
3 node windows 2012 failover cluster
sql2012 installed on node 1 and node 2

node 1 and node 2 -> instance 1 using V: on san as clustered storage
from node 1 v: drive information (get-disk ## | select-object *)
* IsClustered : True

node 3 -> no instance yet using V: on san as standalone storage
from node 3 v: drive information (get-disk ## | select-object *)
* IsClustered : False

To set the drive letter to V: in 2012 as V: is already in the cluster we had to use "Computer Manager"

I'm thinking the SQL install is seeing the cluster V: and not the local V:

So, how to get SQL to see the local V: and *should* SQL be installed on the local V: instead of an available drive letter.


Error message when trying to install SQL on node 3 V:
The directory V:\{path} is not a valid path. Standalone SQL Server on WFC cluster cannot have the files on shared disk locations.
Marios Philippopoulos
Marios Philippopoulos
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12606 Visits: 3766
david.puckett 38841 (7/25/2014)
3 node windows 2012 failover cluster
sql2012 installed on node 1 and node 2

node 1 and node 2 -> instance 1 using V: on san as clustered storage
from node 1 v: drive information (get-disk ## | select-object *)
* IsClustered : True

node 3 -> no instance yet using V: on san as standalone storage
from node 3 v: drive information (get-disk ## | select-object *)
* IsClustered : False

To set the drive letter to V: in 2012 as V: is already in the cluster we had to use "Computer Manager"

I'm thinking the SQL install is seeing the cluster V: and not the local V:

So, how to get SQL to see the local V: and *should* SQL be installed on the local V: instead of an available drive letter.


Error message when trying to install SQL on node 3 V:
The directory V:\{path} is not a valid path. Standalone SQL Server on WFC cluster cannot have the files on shared disk locations.



You need to:

(1) Evict the standalone node from the WSFC cluster
(2) Install the sql on that node
(3) Add the node back to the cluster.

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53689 Visits: 17672
Marios Philippopoulos (7/29/2014)

You need to:

(1) Evict the standalone node from the WSFC cluster
(2) Install the sql on that node
(3) Add the node back to the cluster.

Be very careful here, when you introduce an FCI into a cluster that is to be used for AlwaysOn Availability groups a number of restrictions apply.
The cluster is checking existing groups and has found that a clustered instance of SQL Server already exists on the drive\volume V:\
What happens if at a later date an administrator comes along and runs the add node wizard on one of these cluster nodes?

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

"Ya can't make an omelette without breaking just a few eggs" ;-)
Brandie Tarvin
Brandie Tarvin
SSC-Dedicated
SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)SSC-Dedicated (37K reputation)

Group: General Forum Members
Points: 37671 Visits: 9268
I still need to re-read this article a few times to make sure I understand everything, but I do have one question after the first read through. When combining FCI and Availability Groups, are stand alone (non FCI) servers required? Or is that just how you designed this particular example?

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search