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


SQL Server 2017 Availability group without Windows Server Failover Clustering


SQL Server 2017 Availability group without Windows Server Failover Clustering

Author
Message
stuli3
stuli3
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 26

Hi,

I would like create az availability group without Windows Server Failover Clustering.

I have a primary server and a secondary with SQL Server Enterprise 2017.

I have done availability group but when I trying join secondary server to the group it is drop an error: "An attempt to fail over or create an availability group failed. This operation is not supported when AlwaysOn Availability Groups is running under a remote Windows Server Failover Clustering (WSFC) cluster context. Under a remote cluster context, failing over or creating availability groups are not supported. (Microsoft SQL Server, Error: 19417)"

I cannot what I can do it. Please help me!


Steve Jones
Steve Jones
SSC Guru
SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)

Group: Administrators
Points: 562651 Visits: 20830
An Availabilty Group requires WSFC. It does not require a Failover Clustered Instance (FCI), which is a SQL Server cluster.

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/failover-clustering-and-always-on-availability-groups-sql-server

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
NJ-DBA
NJ-DBA
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11875 Visits: 1653
Do I really get to correct Steve Jones? Nah, I must be wrong.... SQL Server 2017 doesnt strictly require WSFC for AlwaysOn AGs. For example, on Linux there is no WSFC but AGs work fine using the "EXTERNAL" option in the wizard. I must confess that I've not set it up without a cluster, but I bet it would work. This guy is doing it: http://sqlha.com/2017/02/22/alwayson-availability-groups-no-underlying-cluster-sql-server-v-next/ here is another approach: http://www.sqlmastersconsulting.com.au/SQL-Server-Blog/sql-server-2017-read-scale-out-availability-group

MS documentation: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/read-scale-availability-groups

In any event, I dont think you are getting automatic failover without the cluster though.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)SSC Guru (562K reputation)

Group: Administrators
Points: 562651 Visits: 20830
NJ-DBA - Monday, December 11, 2017 7:01 AM
Do I really get to correct Steve Jones? Nah, I must be wrong.... SQL Server 2017 doesnt strictly require WSFC for AlwaysOn AGs. For example, on Linux there is no WSFC but AGs work fine using the "EXTERNAL" option in the wizard. I must confess that I've not set it up without a cluster, but I bet it would work. This guy is doing it: http://sqlha.com/2017/02/22/alwayson-availability-groups-no-underlying-cluster-sql-server-v-next/ here is another approach: http://www.sqlmastersconsulting.com.au/SQL-Server-Blog/sql-server-2017-read-scale-out-availability-group

MS documentation: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/read-scale-availability-groups

In any event, I dont think you are getting automatic failover without the cluster though.

You do, and that's cool. Didn't realize that was working. I thought there was still a WSFC involved.

I'll have to give that a try, though I know Allan has had issues with some of the newer AG stuff as it's been released. There must be something else with the OP that missed earlier in the steps. I'll confess I haven't tried this, but perhaps this is something I need to do in Jan when I'm back in the office.


Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)

Group: General Forum Members
Points: 202734 Visits: 18548
stuli3 - Thursday, December 7, 2017 5:53 AM

Hi,

I would like create az availability group without Windows Server Failover Clustering.

I have a primary server and a secondary with SQL Server Enterprise 2017.

I have done availability group but when I trying join secondary server to the group it is drop an error: "An attempt to fail over or create an availability group failed. This operation is not supported when AlwaysOn Availability Groups is running under a remote Windows Server Failover Clustering (WSFC) cluster context. Under a remote cluster context, failing over or creating availability groups are not supported. (Microsoft SQL Server, Error: 19417)"

I cannot what I can do it. Please help me!

Under sql server 2016 and Windows 2016 it is possible to deploy workgroup clusters or multi domain clusters as well as traditional single domain clusters.
These extra options put the cluster outside of Active Directory, DNS becomes the cluster registry. This is where we start to see the features appearing that sql server 2017 provides.

Under SQL server 2017 vnext it is possible to create a clusterless AG, but it's not without restrictions and pretty much only suitable for read only or test purposes at present.
This technology is heavily evolving and will likely change extensively through future releases as Microsoft "get it right"


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

"Ya can't make an omelette without breaking just a few eggs" ;-)
NJ-DBA
NJ-DBA
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11875 Visits: 1653
I've been working with SQL Server 2017 Distributed Availability Groups and (cross domain). I have 2 nodes in a cluster in domain A doing syncronous replication, and two nodes domain b doing async replication and then a Dist AG between the group in domain A and the group in domain B... it just works. I followed these steps:

Endpoint setups:

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/domain-independent-availability-groups

AlwaysOn config:

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-distributed-availability-groups


The biggest problem I have is that performance with syncronous replication is pretty bad for inserts and updates.
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