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 repointing. With ZRS, your data is still accessible for both read and write operations even if a zone becomes unavailable. ZRS offers durability for storage resources 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 storage account synchronously across three Azure availability zones in the primary region. While it's possible to create a storage account for Azure unmanaged disks that uses GRS, it isn't recommended due to potential issues with consistency over asynchronous geo-replication.
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 storage account 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. For applications requiring high availability, Microsoft recommends using ZRS in the primary region, and also replicating to a secondary region. Zone-redundant storage (ZRS) copies your data synchronously across three Azure availability zones in the primary region.LRS is the least expensive replication option, but isn't recommended for applications requiring high availability or durability. Locally redundant storage (LRS) copies your data synchronously three times within a single physical location in the primary region.Azure Storage offers two options for how your data is replicated in the primary region:
Redundancy in the primary regionĭata in an Azure Storage account is always replicated three times in the primary region. You may want to isolate different types of resources in separate storage accounts if they have different redundancy requirements. All storage resources deployed in the same storage account have the same redundancy setting.
The redundancy setting for a storage account is shared for all storage services exposed by that account. For more information about Azure Storage accounts, see Storage account overview. The storage account represents a shared pool of storage that can be used to deploy storage resources such as blob containers (Blob Storage), file shares (Azure Files), tables (Table Storage), or queues (Queue Storage). The services that comprise Azure Storage are managed through a common Azure resource called a storage account. The features and regional availability described in this article are also available to accounts that have a hierarchical namespace (Azure Blob storage).
0 kommentar(er)
