问题描述
当我们创建具有可用区冗余的VM时，我们必须从3个可用区中的1个中进行选择。假设AzureVM1部署在区域1中。
但是，在创建IP或VPN网关时，我们可以选择"Zone Redundant"，或者明确设置特定的可用区。
我想知道当我们选择"Zone Redundant"时，这里的含义是什么，然后将IP或网关连接到AzureVM1。 "主/活动实例"是否可能？ IP /网关最终位于不同的可用区域，
表示区域2，因此降低了网络性能？或者Azure的后端是否足够聪明，总是尝试将它们部署在与VM相同的区域中，并且只回退到其他区域以实现冗余？
如果IP /网关最终进入不同的可用区域，我们可以预期多少额外的延迟/性能开销？
When we create VMs with availability zone redundancy, we must choose from 1 of the 3 availability zones. Let's say AzureVM1 is deployed in zone 1.
However, when creating IPs or VPN gateways, we can select "Zone Redundant", or explicitly set a specific availability zone.
I want to know what is the implication here when we choose "Zone Redundant", then connect the IP or gateway to AzureVM1. Is it possible for the "main/active instance" of the IP/gateway to end up being in a different availability zone, say zone 2, and therefore have reduced network performance? Or is Azure's backend smart enough to always try to deploy them in the same zone as the VM, and only fall back to other zones for redundancy?
If the IPs/gateways do end up in different availability zones, how much extra latency/performance overhead can we expect?
这篇关于澄清Azure可用区和区域冗余IP，VPN网关等的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！