Azure可用性集，故障域和更新域

我正确吗?这些更新/故障域令人困惑解决方案 我的逻辑是足以将它们置于不同的更新和错误中 域是的，我们应该将VM置于不同的更新和故障域中.我们将它们放在不同的更新域中，当Azure主机需要更新时，Microsoft工程师将更新一个更新域，完成后将更新另一个更新域.这样，我们的虚拟机将不会同时重新启动.我们将它们放在不同的故障域中，当发生意外停机时，该故障域中的虚拟机将重新启动，其他虚拟机将继续运行，这样，在这些虚拟机上运行的应用程序将保持运行状况.要进行射击，请将VM添加到具有不同更新域和故障域的可用性集，这将获得较高的SLA，但这并不意味着一个VM将不会重新引导.希望有帮助. I'm Azure newbie and need some clarifications:When adding machines to Availability set, in order to prevent VM from rebooting, what's best strategy for VM's, put them in:-different update and fault domains-same update domain-same fault domain ?My logic is that it's enough to put them in diffrent update AND fault domainI used this as reference:https://blogs.msdn.microsoft.com/plankytronixx/2015/05/01/azure-exam-prep-fault-domains-and-update-domains/Am i correct ?These update/fault domains are confusing 解决方案 My logic is that it's enough to put them in diffrent update AND fault domainYou are right, we should put VMs in different update and fault domain.We put them in different update domain, when Azure hosts need update, Microsoft engineer will update one update domain, when it completed, update another update domain. In this way, our VMs will not reboot in the same time.we put them in different fault domain, when an Unexpected Downtime happened, VMs in that fault domain will reboot, other VMs will keep running, in this way, our application running on those VMs will keep health.To shot, add VMs to an availability set with different update domain and fault domain, that will get a high SLA, but not means one VM will not reboot.Hope that helps. 这篇关于Azure可用性集，故障域和更新域的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！