The following table shows which types of storage accounts support ZRS in which regions: Storage account type For protection against regional disasters, Microsoft recommends using geo-zone-redundant storage (GZRS), which uses ZRS in the primary region and also geo-replicates your data to a secondary region. However, ZRS by itself may not protect your data against a regional disaster where multiple zones are permanently affected. ZRS provides excellent performance, low latency, and resiliency for your data if it becomes temporarily unavailable. The following diagram shows how your data is replicated across availability zones in the primary region with ZRS: ZRS is also recommended for restricting replication of data to within a country or region to meet data governance requirements. Microsoft recommends using ZRS in the primary region for scenarios that require high availability. The write operation returns successfully only after the data is written to all replicas across the three availability zones. When designing applications for ZRS, follow practices for transient fault handling, including implementing retry policies with exponential back-off.Ī write request to a storage account that is using ZRS happens synchronously. These updates may affect your application if you access data before the updates have completed. If a zone becomes unavailable, Azure undertakes networking updates, such as DNS re-pointing. With ZRS, your data is still accessible for both read and write operations even if a zone becomes unavailable. ZRS offers durability for Azure Storage data objects of at least 99.9999999999% (12 9's) over a given year. Each availability zone is a separate physical location with independent power, cooling, and networking. Zone-redundant storage (ZRS) replicates your Azure Storage data synchronously across three Azure availability zones in the primary region. For more information on paired regions, see Azure regions. In some cases, the paired regions across which the data is geo-replicated may be in another country or region. If your application is restricted to replicating data only within a country or region due to data governance requirements, you may opt for LRS.If your application stores data that can be easily reconstructed if data loss occurs, you may opt for LRS.LRS is a good choice for the following scenarios:
The following diagram shows how your data is replicated within a single data center with LRS: The write operation returns successfully only after the data is written to all three replicas. To mitigate this risk, Microsoft recommends using zone-redundant storage (ZRS), geo-redundant storage (GRS), or geo-zone-redundant storage (GZRS).Ī write request to a storage account that is using LRS happens synchronously. However, if a disaster such as fire or flooding occurs within the data center, all replicas of a storage account using LRS may be lost or unrecoverable. LRS protects your data against server rack and drive failures.
LRS is the lowest-cost redundancy option and offers the least durability compared to other options. LRS provides at least 99.999999999% (11 nines) durability of objects over a given year. Locally redundant storage (LRS) replicates your data three times within a single data center in the primary region. Microsoft recommends using ZRS in the primary region for Azure Data Lake Storage Gen2 workloads.
0 kommentar(er)
