Start here! Get your feet wet with the Microsoft cloud and begin your journey to earning your Microsoft Certified: Azure Fundamentals certification!
Azure storage redundancy helps ensure high availability and data resilience by keeping multiple copies of your data. This practice protects against hardware failures, network problems, or even larger regional outages. Choosing the right option depends on balancing your data's criticality, your budget, and any compliance rules you must follow.
A decision tree that branches on cross-region disaster recovery needs, zone-level protection, and read access to a secondary region to select the appropriate Azure Storage redundancy option.
Azure offers several main redundancy models:
Your choice should match the business scenario. For example, development or test environments often use LRS because it is the most affordable. Applications needing high availability within a single region but not cross-region failover are a good fit for ZRS. Mission-critical workloads that must survive a complete regional outage require GRS or RA-GRS. Higher redundancy levels like RA-GRS cost more but provide better recovery targets, meaning less data loss and downtime after a failure.
Azure Storage provides four primary redundancy strategies: Locally Redundant Storage (LRS), Zone-Redundant Storage (ZRS), Geo-Redundant Storage (GRS), and Read-Access Geo-Redundant Storage (RA-GRS). Each uses a different replication method and scope, offering a trade-off between cost, performance, and data durability.
Locally Redundant Storage (LRS) is the simplest and most cost-effective option. It creates three copies of your data on separate hardware within a single Azure datacenter. This protects against local hardware failures like a disk crash but does not guard against an outage affecting the entire facility. LRS is suitable for non-critical workloads or data that can be easily recreated.
Zone-Redundant Storage (ZRS) provides higher availability within a single region. It also maintains three copies, but spreads them across multiple availability zones, which are separate physical locations with independent power and networking. This protects against a failure in one entire zone. ZRS offers stronger resilience than LRS for production workloads that need to stay online within a region.
Geo-Redundant Storage (GRS) and Read-Access Geo-Redundant Storage (RA-GRS) are designed for disaster recovery. Both create six total copies: three in your primary region and three in a paired secondary region hundreds of miles away. GRS keeps the secondary copies offline for failover use only. RA-GRS adds the benefit of read-only access to the secondary copies, which can improve performance for global applications. These are the best options for critical data that must survive a major regional event.
Locally Redundant Storage (LRS) is Azure's basic replication option. It stores three copies of your data within the same data center where your storage account is located. This replication uses a rack-aware design, meaning the copies are placed on separate hardware nodes across different physical racks. This protects your data from common hardware failures like a server or disk malfunction.
Because all copies are kept in one facility, LRS is the most cost-effective redundancy option. It avoids the bandwidth and storage costs associated with copying data across regions. This makes it a simple and affordable choice for scenarios where data is not mission-critical, such as development, testing, or storing easily reproducible data.
The main limitation of LRS is its lack of protection against a datacenter-wide outage. If the entire facility experiences a power failure, fire, or other disaster, your data becomes unavailable. LRS also provides no geo-failover capability or read access from another location. For applications that require higher availability, you must choose a more resilient option like ZRS or GRS.
Zone-Redundant Storage (ZRS) replicates your data across multiple availability zones within a single Azure region. Like LRS, it maintains three copies of your data, but it ensures those copies are stored in separate physical facilities, each with its own independent power, cooling, and networking. This design provides protection against a failure impacting an entire availability zone.
ZRS offers higher availability than LRS because it can survive an outage in one zone while keeping your data accessible from the other zones. However, its scope is still regional; it does not replicate data to a different geographic region. This makes ZRS a balanced choice for mission-critical applications that need strong uptime within a region but do not require cross-region disaster recovery.
Compared to other options, ZRS provides more resilience than LRS but less geographic failover than GRS. It does not allow read access from a secondary location like RA-GRS does. ZRS is well-suited for production workloads where low latency and high throughput within a region are priorities, and where the cost and complexity of a full geo-redundant solution are not necessary.
Geo-Redundant Storage (GRS) and Read-Access Geo-Redundant Storage (RA-GRS) are Azure's solutions for cross-region disaster recovery. Both options asynchronously replicate your data to a secondary Azure region located hundreds of miles from the primary region. They each maintain a total of six copies: three in the primary region and three in the secondary region, providing excellent durability against a major regional outage.
The key difference between GRS and RA-GRS is access to the secondary copies. With standard GRS, the data in the secondary region is used only for failover recovery; you cannot read from it unless Microsoft initiates a failover due to a primary region outage. RA-GRS adds read-only access to the secondary copies at all times. This allows applications to retrieve data from the secondary region, which can reduce read latency for users located geographically closer to it.
Choosing between GRS and RA-GRS depends on your access needs and performance goals. Use GRS for a cost-effective disaster recovery strategy where you only need the secondary data for emergency failover. Choose RA-GRS when your global application can benefit from lower-latency read operations or when you want the flexibility to read from the secondary region for reporting or load balancing, even during normal operations. RA-GRS comes at a higher cost due to this added read capability.
Prepare and test your skills
Prepare and test your skills
Locally Redundant Storage (LRS) stores three copies of your data within a single Azure data center on separate hardware nodes across different physical racks. It is the most cost-effective redundancy option and is suitable for development or test environments, non-critical workloads, or data that can be easily recreated.
Zone-Redundant Storage (ZRS) replicates data across multiple availability zones within a single Azure region, while LRS keeps all three copies in a single data center. ZRS provides protection against a failure affecting an entire availability zone, offering higher availability than LRS for production workloads that need to stay online within a region.
Geo-Redundant Storage (GRS) keeps secondary copies offline for failover use only, while Read-Access Geo-Redundant Storage (RA-GRS) allows read access to the secondary copies at all times. RA-GRS enables applications to retrieve data from the secondary region, which can reduce read latency for globally distributed users.
Choose GRS or RA-GRS when your data must survive a complete regional outage, as both maintain six total copies across a primary and secondary region hundreds of miles apart. Use GRS for cost-effective disaster recovery where you only need secondary data for emergency failover, and RA-GRS when your application can benefit from lower-latency reads or flexible secondary access for reporting and load balancing.
An organization hosts mission-critical business reports in an Azure Storage account. The organization requires protection against regional disasters by copying data asynchronously to a secondary paired region hundreds of miles away.
In addition, client applications distributed globally need immediate, continuous read access to the data in the secondary region at all times, without waiting for or initiating an account failover.
Which Azure Storage redundancy option should the organization select?
StudyCerts
StudyCerts