Azure Storage - Storage Redundancy
Embedded Files
Synchronous replication means data is copied in real-time, ensuring all copies are identical at any given moment.
Asynchronous replication involves a delay, with data copied to secondary locations after it's written to the primary location, leading to potential differences between copies at a given time.
Locally Redundant Storage (LRS)
Replicates your data three times within a single datacenter in the primary region.
LRS can be chosen when you want a cost-effective replication strategy and your data can be regenerated if a data center failure occurs.
For instance, non-critical, derivative, or easily-recreatable data.
Zone-Redundant Storage (ZRS)
Replicates your data across three separate availability zones in the primary region which ensures that even if one data center in a zone experiences a failure, the data remains accessible and available for writes.
Choose ZRS for applications that require high availability without having to replicate data to a secondary region.
A good fit for mission-critical applications with region-focused users, like a regional content delivery platform.
Geo-Redundant Storage (GRS)
Uses LRS in the primary region and asynchronously replicates the data to a secondary region, ensuring durability even during a regional disaster.
When your application is globally distributed and needs to store critical data, GRS is the way to go.
For example, in a global e-commerce platform where loss of data could result in financial losses and legal implications.
Read-Access Geo-Redundant Storage (RA-GRS)
GRS with provided read access to the data in the secondary region, adding an extra layer of availability.
Geo-Zone-Redundant Storage (GZRS)
Combines ZRS in the primary region with asynchronous replication to a secondary region.
Read-Access Geo-Zone-Redundant Storage (RA-GZRS)
GZRS with provided read access to the data in the secondary region, adding an extra layer of availability.
Distinct feature of RA-GRS and RA-GZRS is that it provides read access to the data in the secondary region at all times, not just when there is an outage in the primary region. This ensures that your data is available for reading, even during disruptions or issues affecting the primary region, thereby enhancing data availability without waiting for a formal failover to be initiated by Microsoft.
Sample Use Case Scenario: Streaming Media Platform
Imagine a streaming media platform that serves video content to users across the globe. The platform needs to ensure that users have uninterrupted access to media files even when there are issues or disruptions in one of the regions. The application relies heavily on reading data (video files, user profiles, etc.) from the storage account.
With RA-GRS, if there are issues in the primary region (e.g., network disruptions, partial outages, etc.), the application can still read from the secondary region, ensuring users have uninterrupted access to video content. Even if there's a complete outage in the primary region, applications can switch to read data from the secondary region while Microsoft works on failover processes, maintaining access to content for users.
While GRS will protect data by replicating it to a secondary region, it doesn’t offer read access to data in the secondary region unless a failover is initiated by Microsoft during a complete regional outage. There could be scenarios where there are disruptions or degraded performance in the primary region, which doesn’t trigger a full failover but might impact user experience.
Source:
https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy
https://learn.microsoft.com/en-us/azure/storage/common/storage-disaster-recovery-guidance
Page updated
Google Sites
Report abuse