Zonal resources, once created, cannot be moved to other availability zones within the region. However when placing a VM in an availability zone, you have to specify its zone. When placing a VM in an availability set, you cannot specify its placement (fault domain, update domain etc). However an availability zone imposes no such restrictions (zonal VMs can belong to any VNET and any resource group within the region). With an availability set, all VMs in it must belong to the same VNET and same resource group. SLA for VMs in availability zones is predictably higher (99.99% uptime guarantee) than that of VMs in availability sets (99.95% uptime guarantee). The former shields you against hardware failures in a physical rack, while the latter shields you against a datacenter-level disaster. Load balancers with basic sku are non-zonal.Īvailability sets provide redundancies within a datacenter, while availability zones provide redundancies within a region. Load Balancers (standard sku only): During creation, load balancers (standard sku only) can be configured as zone-redundant or zonal. We already covered ZRS storage in part 5 of this blog series. Storage Accounts: With zone-redundant storage, your data is replicated across three availability zones within the same region. Public IPs: During creation, a Public IP address (standard sku only) can be configured as zone-redundant (default) or zonal. Snapshots of any managed disks (zonal or otherwise) can be be persisted to zone-redundant storage. Managed Disks: During creation, a managed disk can be configured as zonal or non-zonal. Its managed disk and public IP address (standard sku only) are then automatically placed in that same zone. Virtual Machines: During creation, a VM can be configured as zonal. Only a few Azure resource types support availability zones (we’re highlighting a couple of important ones below. If you haven’t seen that post, please take a minute to do so.Īvailability zones exist to shield your resources against a datacenter-level disaster.Īs of the time of writing this blog post, only a few Azure regions support availability zones.Īvailability zones are free (you’re only charged for the VMs and resources placed in the availability zones). In the opening post of this blog series we talked about availability zones and how resources can be classified as zone-redundant, zonal (zone-specific) or non-zonal (regional). Each of those topics deserve their own series, perhaps I’ll write about them in the future if time permits. I’ll not be addressing scaling (horizontal or vertical), backups/restores and resiliency/healing in these posts. Note: This blog post is part of a series centered around the topic of high availability in Azure: Awesome azure devops resources High Availability in Azure: Availability Zones Published on by Mithun Shanbhag
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |