Edit

Share via

Redundancy options for managed disks

  • Article

Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets

Azure managed disks offer two storage redundancy options, zone-redundant storage (ZRS), and locally redundant storage. ZRS provides higher availability for managed disks than locally redundant storage (LRS) does. However, the write latency for LRS disks is better than ZRS disks because LRS disks synchronously write data to three copies in a single data center.

Locally redundant storage for managed disks

Locally redundant storage (LRS) replicates your data three times within a single data center in the selected region. LRS protects your data against server rack and drive failures. LRS disks provide at least 99.999999999% (11 9's) of durability over a given year. To protect an LRS disk from a zonal failure like a natural disaster or other issues, take the following steps:

  • Use applications that can synchronously write data to two zones, and automatically failover to another zone during a disaster.
    • An example would be SQL Server Always On.
  • Take frequent backups of LRS disks with ZRS snapshots.
  • Enable cross-zone disaster recovery for LRS disks via Azure Site Recovery. However, cross-zone disaster recovery doesn't provide zero Recovery Point Objective (RPO).

If your workflow doesn't support application-level synchronous writes across zones, or your application must meet zero RPO, then ZRS disks would ideal.

Zone-redundant storage for managed disks

Zone-redundant storage (ZRS) synchronously replicates your Azure managed disk across three Azure availability zones in the region you select. Each availability zone is a separate physical location with independent power, cooling, and networking. ZRS disks provide at least 99.9999999999% (12 9's) of durability over a given year.

A ZRS disk lets you recover from failures in availability zones. If a zone went down and your virtual machine (VM) wasn't affected, then your workloads continue running. But if your VM was affected by an outage and you want to recover before it's resolved, you can force detach your ZRS disks from the failed VM, freeing them to attach to another VM.

ZRS disks can also be shared between VMs for improved availability with clustered or distributed applications like SQL FCI, SAP ASCS/SCS, or GFS2. A shared ZRS disk can be attached to primary and secondary VMs in different zones to take advantage of both ZRS and availability zones. If your primary zone fails, you can quickly fail over to the secondary VM using SCSI persistent reservation.

For more information on ZRS disks, see Zone Redundant Storage (ZRS) option for Azure Disks for high availability.

Limitations

ZRS for managed disks is only supported with Premium SSD and Standard SSD managed disks. ZRS for managed disks isn't supported with Premium SSD v2 managed disks. Force detach only supports data disks.

Regional availability

ZRS disks are currently available in the following regions:

  • South Africa North
  • East Asia
  • Southeast Asia
  • Australia East
  • US Gov Virginia
  • Brazil South
  • Canada Central
  • China North 3
  • North Europe
  • West Europe
  • France Central
  • Germany West Central
  • Central India
  • Israel Central
  • Italy North
  • Japan East
  • Korea Central
  • Norway East
  • Poland Central
  • Qatar Central
  • Sweden Central
  • Switzerland North
  • UAE North
  • UK South
  • Central US
  • East US
  • East US 2
  • South Central US
  • West US 2
  • West US 3

Billing implications

For details see the Azure pricing page.

Comparison with other disk types

Except for more write latency, disks using ZRS are identical to disks using LRS, they have the same scale targets. Benchmark your disks to simulate the workload of your application and compare the latency between LRS and ZRS disks.

Next steps