SQL Always-on与不同的区域 [英] SQL Always-on with different region

查看:85
本文介绍了SQL Always-on与不同的区域的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

嗨。我正在查看以下链接,


解决方案


多站点AlwaysOn就像你上面那样,你仍然需要一个文件共享见证。 这是因为你希望1区成为你的H.A.和区域2是DR(你想手动调用的DR),所以区域1中的Quorum
仍然需要文件共享见证(我希望这有意义吗?)


您是正确的,如果区域1完全停止(不要忘记该区域可能是3个数据中心,您可以将SQL服务器分离到该区域中的不同数据中心),那么群集将处于脱机状态。 如果发生这种情况,那么
将需要在DR节点上手动强制群集联机。 但这是此设置的最佳做法,因为您的DR节点很远。


2。不,您不应该在VM上使用多域。 在这里使用一个覆盖2个区域的域名。


我希望有帮助吗?


谢谢,


马特


Hi . I am looking into the following links ,

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-dr

And would like to have some question :

1. Fileshare witness is still need for this case ? What I think is Azure region containing the witness is down, the whole cluster should be down already .

2. is it support multiple domain ? for example domain A.com for the first region and domain B.com for the second region  

解决方案

Hi,

For a multi-site AlwaysOn like you have above then you would still want a File Share Witness.  This is because you want Region 1 to be your H.A. and Region 2 to be DR (DR you want to invoke manually), so the File Share witness is still needed for Quorum in Region 1 (I hope that makes sense?)

You are correct that if Region 1 entirely goes down (don't forget that the region is a probably 3 data centres and you can separate your SQL servers over different data centres in the region) then the cluster will be offline.  If this happens then you would need to manually force the cluster online on the DR node.  But this is best practice for this set-up as your DR node is far away.

2. No you shouldn't use multi-domain on the VMs.  Have 1 domain that stretches over the 2 regions to use here.

I hope that helps?

Thanks,

Matt


这篇关于SQL Always-on与不同的区域的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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