在Azure中的Windows Server 2016上配置多实例SQL故障转移群集 [英] Configuring a Multi Instance SQL Failover Cluster on Windows Server 2016 in Azure
问题描述
我目前正在使用2个在Azure VM上运行Windows Server 2016的节点设置故障转移群集.我们需要运行4个SQL Server实例.
我设法按照本指南操作了1个实例:https://docs.microsoft.com/zh-CN/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql -create-failover-cluster
但是，当我添加实例编号2时，负载平衡器开始出现大量问题.我似乎无法在同一节点上运行2个实例，并且无法远程访问.为了澄清起见，我可以将它们都运行在同一节点之外，但是只有其中之一 将可以从主机节点以外的任何地方访问它.
如果两个实例都托管在单独的节点上，则可以访问这两个实例，但是由于两种许可方式，这都是不可接受的，而且事实上我需要4个实例，并且只有2个节点.
我们发现两个实例都配置有不同的端口，不同的运行状况探针端口和不同的后端池，因为我们发现它们不能仅在具有一组网络接口的同一台计算机上运行.
我在任何地方都找不到任何文档.
干杯
Oliver
尽管您可以从技术上在一台计算机上安装多个SQL实例，但我认为这不会起作用在Azure中非常好. SQL是占用大量CPU和RAM的程序，并且具有多个实例可能会导致问题.此外， 正如您在负载平衡器中看到的那样，您只能有1-1端口映射.
因此您不必说VM1端口443映射到VM中的两个不同端口.它只能映射到VM的一个端口.因此，您将只能在VM内访问SQL的单个实例.您可能可以通过更改来解决此问题 两个sql实例的端口.或添加一个额外的负载平衡器.但同样，性能可能会成为一个问题，我可能会感到困惑，因为您必须记住要使用哪个LB以及为哪个SQL实例分配了非默认端口.
如果您需要4个实例，那么您实际上应该有4个专用节点.每个SQL实例一个.然后，使用负载平衡器映射4个VM.
有人在服务器故障中也提出了类似的问题
我建议回顾一下我们在Azure VM中运行SQL的最佳实践
此外，我们在Azure中提供SQL，而无需弄乱您可能会更有用的基础结构
Hi,
I'm currently setting up a Failover Cluster with 2 nodes running Windows Server 2016 on Azure VMs. We need to run 4 SQL Server Instances.
I managed to get 1 instance working as per this guide: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-create-failover-cluster
However when I added instance number 2, I started having massive issues with the load balancer. I seemingly can't have 2 instances running on the same node and be accessible remotely. To clarify, I can run them both off the same node, however only 1 of them will be accessible from anywhere other than the host node.
Both instances are accessible if they are hosted on seperate nodes, however this is not acceptable due to both licensing, and the fact I need 4 instances and only have 2 nodes.
We have both instances configured with different ports, different health probe ports and different backend pools as we found that they would not run on the same machine with just the set of network interfaces.
I can't find any documentation for this anywhere.
Cheers,
Oliver
Although you can technically install multiple SQL instances on one machine I don't believe that is something that will work very well in Azure. SQL is an CPU and RAM intensive program and having multiple instance will likely cause problems. In addition, as you are seeing with the load balancer, you can only have a 1-1 port mapping.
So you can't have say VM1 port 443 mapped to two different ports in the VM. It would only be able to be mapped to one port of the VM. So you would only be able to access a single instance of SQL inside the VM. You might be able to work around this by changing the ports for the two sql instances. Or adding an additional load balancer. But again, performance would likely be an issue and I could see it getting confusing as you would have to remember which LB to use and which SQL instance has non-default ports assigned.
If you need 4 instances then you really should have 4 dedicated nodes. One per SQL instances. Then use the load balancer to map the 4 VMs.
Someone asked a similar question in Server fault as well
I would suggest reviewing our best practices for running SQL in an Azure VM
Also, we offer SQL in Azure without the need to mess with the infrastructure which you might be more useful
这篇关于在Azure中的Windows Server 2016上配置多实例SQL故障转移群集的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
