Distributed AG是否需要Windows群集? [英] Does Distributed AG need windows clustering?

查看:90
本文介绍了Distributed AG是否需要Windows群集?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


简单问题 - 分布式AG是否需要Windows集群?



------



来自  https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always- on-availability?view = sql-server-2017



" SQL Server 2016引入了分布式可用性组。在分布式
可用性组中,两个可用性组驻留在不同的集群上。"



---



看起来好像需要Windows聚类吗?



---



我问的原因是我们有一个主服务器,其中有集群,我们已经设置AG。现在,还有另一个独立的(没有Windows集群)服务器
用于报告,但由于它没有Windows集群 - 我们无法在事务性sql集群和这个独立的报告sql框之间设置AG而没有Windows集群吗?





---



只是一个是或否与适当的链接就足够了,谢谢。




D

解决方案

嗯,语法是:


CREATE AVAILABILITY GROUP group_name    WITH(< with_option_spec> [, ... n))    FOR [DATABASE database_name [,... n]]    REPLICA ON< add_replica_spec> [,... n]  - >  ;  AVAILABILITY
GROUP ON< add_availability_group_spec> [,... 2]    [LISTENER'dn_name'(< listener_option>)]  [;] 


您添加的是可用性组,因此您无法使用该单个服务器。


从SQL 2017开始,您可以创建无群集可用性组。但是,请记住,这不是针对高可用性解决方案,而是针对那些可能希望AG进行测试但又不想在Windows群集上设置
的人。
无论你是否可以将无集群AG添加到分布式AG,我都不这么认为,因为语法需要一个监听器,而监听器只能用于Windows集群。


Hi, Simple question - Does distributed AG need windows clustering?

------

From https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-2017

"SQL Server 2016 introduces distributed availability groups. In a distributed availability group two availability groups reside on different clusters."

---

So looks like it does need windows clustering right?

---

Reason i ask is we have a main server where clustering is there & we have setup AG. Now, there is another stand-alone (no windows clustering) server which is to be used for reporting, but as it doesn't have windows clustering - we cannot setup AG between the transactional sql cluster & this stand alone reporting sql box with no windows clustering right?

---

just a yes or no with appropriate link will suffice, thanks.


D

解决方案

Well, the syntax is:

CREATE AVAILABILITY GROUP group_name     WITH (<with_option_spec> [ ,...n ] )     FOR [ DATABASE database_name [ ,...n ] ]     REPLICA ON <add_replica_spec> [ ,...n ]  -->   AVAILABILITY GROUP ON <add_availability_group_spec> [ ,...2 ]     [ LISTENER 'dns_name' ( <listener_option> ) ]  [ ; ] 
What you add is an avilability group, so you cannot use that single server.

Starting with SQL 2017, you can create cluster-less availability groups. Bear in mind, though, that this is not intended for high availability solutions, but more for people who may want an AG to test on, but who don't want to go through hoops of setting up Windows cluster.
Whether you can add a clusterless AG to distributed AG, I don't think so, since the syntax requires a listener, and the listener is only possible with the Windows cluster.


这篇关于Distributed AG是否需要Windows群集?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆