%3CLINGO-SUB%20id%3D%22lingo-sub-1431700%22%20slang%3D%22en-US%22%3EUnderstanding%20Azure%20storage%20redundancy%20offerings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1431700%22%20slang%3D%22en-US%22%3E%3CP%3EBefore%20we%20go%20deeper%20into%20the%20storage%20redundancy%20space%20it'd%20be%20helpful%20to%20better%20understand%20the%20building%20blocks%20of%20Azure%20global%20infrastructure%20as%20well%20as%20a%20few%20terms%20commonly%20used%20in%20high%20availability%20and%20disaster%20recovery%20in%20general.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Data%20residency%20boundary.PNG%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195771iA77FB92BF691027C%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Data%20residency%20boundary.PNG%22%20alt%3D%22Data%20residency%20boundary.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%20class%3D%22lia-align-left%22%3E%3CSTRONG%3EGeography%3C%2FSTRONG%3E%20-%20a%20discrete%20market%2C%26nbsp%3B%3CSPAN%3Etypically%20containing%202%2B%20regions%2C%20that%20preserves%20data%20residency%20and%20compliance%20boundaries.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EAzure%20region%3C%2FSTRONG%3E%20-%20a%20set%20of%20datacenters%20deployed%26nbsp%3B%3CSPAN%3Ewithin%20a%20latency-defined%20perimeter%20and%20connected%20through%20a%20dedicated%20regional%20low-latency%20network.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CSTRONG%3ERegion%20pair%3C%2FSTRONG%3E%20-%20each%20Azure%20region%20is%20paired%20with%20another%20region%20within%20the%20same%20geography.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CSTRONG%3EAvailability%20zone%3C%2FSTRONG%3E%20-%20a%26nbsp%3Bphysically%20separate%20location%20within%20an%20Azure%20region.%20Each%20AZ%20is%20made%20up%20of%201%2B%20datacenters%20with%20independent%20power%2C%20cooling%2C%20and%20networking.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CSTRONG%3EAvailability%3C%2FSTRONG%3E%20-%20defined%20by%20Gartner%20as%20the%26nbsp%3B%3C%2FSPAN%3Ethe%20assurance%20that%20an%20enterprise%E2%80%99s%20IT%20infrastructure%20has%20suitable%20recoverability%20and%20protection%20from%20system%20failures%2C%20natural%20disasters%20or%20malicious%20attacks.%20High%20availability%20refers%20to%20a%20system%20that%20is%20operational%20without%20interruption%20for%20long%20periods%20of%20time%20by%20using%20redundant%20or%20fault-tolerant%20components%20and%20is%20typically%20measured%20as%20a%20percentage.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3ERecovery%20point%20objective%20(RPO)%3C%2FSTRONG%3E%20-%26nbsp%3Bthe%20amount%20of%20data%20which%20can%20be%20lost%20while%20bringing%20the%20system%20back%20online%20after%20a%20critical%20failure%2C%20i.e.%20the%20point%20in%20time%20to%20which%20the%20data%20can%20be%20recovered.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3ERecovery%20time%20objective%20(RTO)%3C%2FSTRONG%3E%20-%26nbsp%3Bthe%20amount%20of%20time%20that%20it%20takes%20to%20get%20the%20system%20back%20online%20after%20a%20critical%20failure%2C%20i.e.%20how%20long%20you%20can%20sustain%20a%20service%20interruption%20before%20you%20absolutely%20need%20to%20be%20back%20online.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20these%20in%20mind%20let's%20take%20a%20closer%20look%20at%20what%20Azure%20storage%20redundancy%20options%20have%20to%20offer.%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-center%22%3ELocally%20redundant%20storage%20(LRS)%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22LRS.PNG%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195774i6CC524F59559A20D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22LRS.PNG%22%20alt%3D%22LRS.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EData%20is%20synchronously%20replicated%203%20times%20within%20a%20single%20storage%20cluster%2C%20in%20a%20single%20data%20center%20in%20a%20region%20%3D%20%3CSTRONG%3Ecan%20only%20sustain%20node%20failure%20within%20the%20storage%20cluster.%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EProvides%20at%20least%2011%209s%20of%20durability%20and%2099.9%25%20of%20availability%20(reads%20%26amp%3B%20writes)%20for%20hot%20tier%20and%2099%25%20for%20cool.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20class%3D%22lia-align-center%22%3EZone-redundant%20storage%20(ZRS)%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22ZRS.PNG%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195777i11D8054C01AA9E82%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22ZRS.PNG%22%20alt%3D%22ZRS.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EData%20is%20synchronously%20replicated%203%20times%20across%203%20availability%20zones%20in%20a%20region%20%3D%20%3CSTRONG%3Ecan%20sustain%20node%20failure%20within%20the%20storage%20cluster%20or%20entire%20datacenter%20or%20availability%20zone%20going%20down.%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EProvides%20at%20least%2012%209s%20of%20durability%20and%2099.9%25%20of%20availability%20(reads%20%26amp%3B%20writes)%20for%20hot%20tier%20and%2099%25%20for%20cool.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20class%3D%22lia-align-center%22%3EGeo-redundant%20storage%20(GRS)%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22GRS.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195792iD920119B80CAD3DA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22GRS.PNG%22%20alt%3D%22GRS.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EData%20is%20synchronously%20replicated%203%20times%26nbsp%3Bwithin%20a%20single%20storage%20cluster%20in%20the%20primary%20region%2C%20then%20asynchronously%20replicated%20to%20the%20secondary%20paired%20region%20(3%20more%20copies)%20%3D%26nbsp%3B%3CSTRONG%3Ecan%20sustain%20node%20failure%20within%20the%20storage%20cluster%2C%20entire%20datacenter%20or%20availability%20zone%20going%20down%20or%20a%20region-wide%20outage%20(DC%2Fzone%2Fregion%20failure%20would%20require%20account%20failover%20to%20restore%20read%20and%20write%20availability%20-%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Faccountfailover%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Faccountfailover%3C%2FA%3E).%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EProvides%20at%20least%2016%209s%20of%20durability%20and%2099.9%25%20of%20availability%20(reads%20%26amp%3B%20writes)%20for%20hot%20tier%20and%2099%25%20for%20cool%20%2B%2099.99%25%20on%20reads%20for%20RA-GRS%20(read-access%20to%20the%20secondary%20endpoint).%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3ETypically%20has%20an%20RPO%20of%20less%20than%2015%20minutes%20(no%20SLA).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3ERead%20access%20to%20the%20secondary%20is%20available%20if%20the%20primary%20region%20is%20down%20with%20RA-GRS.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20class%3D%22lia-align-center%22%3EGeo-zone-redundant%20storage%20(GZRS)%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22GZRS.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195795i3D14981AC8D7397C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22GZRS.PNG%22%20alt%3D%22GZRS.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EData%20is%20synchronously%20replicated%203%20times%20across%203%20availability%20zones%20in%20the%20primary%20region%2C%20then%20asynchronously%20replicated%20to%20the%20secondary%20paired%20region%20(3%20more%20copies)%20%3D%26nbsp%3B%3CSTRONG%3Ecan%20sustain%20node%20failure%20within%20the%20storage%20cluster%2C%20entire%20datacenter%20or%20availability%20zone%20going%20down%20or%20a%20region-wide%20outage%20(only%20region%20failure%20would%20require%20account%20failover%20to%20restore%20read%20and%20write%20availability%20-%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Faccountfailover%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Faccountfailover%3C%2FA%3E).%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EProvides%20at%20least%2016%209s%20of%20durability%20and%2099.9%25%20of%20availability%20(reads%20%26amp%3B%20writes)%20for%20hot%20tier%20and%2099%25%20for%20cool%20%2B%2099.99%25%20on%20reads%20for%20RA-GRS%20(read-access%20to%20the%20secondary%20endpoint).%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3ETypically%20has%20an%20RPO%20of%20less%20than%2015%20minutes%20(no%20SLA).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3ERead%20access%20to%20the%20secondary%20is%20available%20if%20the%20primary%20region%20is%20down%20with%20RA-GZRS.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20class%3D%22lia-align-center%22%3EAccount%20failover%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Account%20failover.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195796i105184A5076FD75D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Account%20failover.PNG%22%20alt%3D%22Account%20failover.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAllows%20you%20to%20initiate%20the%20failover%20at%20the%20account%20level%20in%20case%20of%20an%20ongoing%2Fupcoming%20disaster%20(certain%20restrictions%20apply%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fstorage%2Fcommon%2Fstorage-disaster-recovery-guidance%23additional-considerations%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eaccount%20failover%20considerations%3C%2FA%3E).%3C%2FLI%3E%0A%3CLI%20class%3D%22lia-align-left%22%3EGenerally%20available%20in%20all%20public%20regions.%3C%2FLI%3E%0A%3CLI%20class%3D%22lia-align-left%22%3EFailover%20is%20disruptive%20and%20converts%20the%20account%20to%20LRS.%3C%2FLI%3E%0A%3CLI%20class%3D%22lia-align-left%22%3E%3CSPAN%3ETypically%20has%20an%20RTO%20of%20less%201%20hour%20(no%20SLA).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20class%3D%22lia-align-left%22%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Failover%20timeline.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195801i257F9F72E570F63D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Failover%20timeline.PNG%22%20alt%3D%22Failover%20timeline.PNG%22%20%2F%3E%3C%2FSPAN%3E%3CSTRONG%3EBe%20aware%20of%20potential%20data%20loss!%3C%2FSTRONG%3E%26nbsp%3BAlways%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fstorage%2Fcommon%2Flast-sync-time-get%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Echeck%20LastSyncTime%3C%2FA%3E%20before%20executing%20the%20failover.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-left%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-left%22%3EHope%20this%20helps%20you%20get%20a%20good%20grasp%20of%20durability%20and%20availability%20options%20for%20your%20storage%20needs!%20For%20more%20details%20please%20refer%20to%20our%20documentation%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fstorageredundancy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fstorageredundancy%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Faccountfailover%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Faccountfailover%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fstoragehadesign%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fstoragehadesign%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EWe'd%20love%20to%20hear%20from%20you%20-%20please%20reach%20us%20out%20via%20email%20at%26nbsp%3B%3CA%20href%3D%22mailto%3Aazurestoragefeedback%40microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Eazurestoragefeedback%40microsoft.com%3C%2FA%3E%26nbsp%3Band%2For%20post%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F217298-storage%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EAzure%20storage%20feedback%20forum%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1431700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Redundancy.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F195802i3D2493C65750AC62%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Redundancy.PNG%22%20alt%3D%22Redundancy.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EIn%20this%20post%20we'll%20go%20over%20major%20Azure%20infrastructure%20terminology%20aiming%20to%20get%20more%20clarity%20on%20how%20various%20high%20availability%20and%20disaster%20recovery%20offerings%20within%20Azure%20storage%20work%20and%20then%20segway%20to%20discussing%20the%20redundancy%20options%20in%20more%20detail.%20Read%20away!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1431700%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Blob%20Storage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Before we go deeper into the storage redundancy space it'd be helpful to better understand the building blocks of Azure global infrastructure as well as a few terms commonly used in high availability and disaster recovery in general.

Data residency boundary.PNG

  • Geography - a discrete market, typically containing 2+ regions, that preserves data residency and compliance boundaries.
  • Azure region - a set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network.
  • Region pair - each Azure region is paired with another region within the same geography.
  • Availability zone - a physically separate location within an Azure region. Each AZ is made up of 1+ datacenters with independent power, cooling, and networking.
  • Availability - defined by Gartner as the the assurance that an enterprise’s IT infrastructure has suitable recoverability and protection from system failures, natural disasters or malicious attacks. High availability refers to a system that is operational without interruption for long periods of time by using redundant or fault-tolerant components and is typically measured as a percentage.
  • Recovery point objective (RPO) - the amount of data which can be lost while bringing the system back online after a critical failure, i.e. the point in time to which the data can be recovered.
  • Recovery time objective (RTO) - the amount of time that it takes to get the system back online after a critical failure, i.e. how long you can sustain a service interruption before you absolutely need to be back online.

 

With these in mind let's take a closer look at what Azure storage redundancy options have to offer.

Locally redundant storage (LRS)

LRS.PNG

  • Data is synchronously replicated 3 times within a single storage cluster, in a single data center in a region = can only sustain node failure within the storage cluster.
  • Provides at least 11 9s of durability and 99.9% of availability (reads & writes) for hot tier and 99% for cool.

Zone-redundant storage (ZRS)

ZRS.PNG

  • Data is synchronously replicated 3 times across 3 availability zones in a region = can sustain node failure within the storage cluster or entire datacenter or availability zone going down.
  • Provides at least 12 9s of durability and 99.9% of availability (reads & writes) for hot tier and 99% for cool.

Geo-redundant storage (GRS)

GRS.PNG

  • Data is synchronously replicated 3 times within a single storage cluster in the primary region, then asynchronously replicated to the secondary paired region (3 more copies) = can sustain node failure within the storage cluster, entire datacenter or availability zone going down or a region-wide outage (DC/zone/region failure would require account failover to restore read and write availability - https://aka.ms/accountfailover).
  • Provides at least 16 9s of durability and 99.9% of availability (reads & writes) for hot tier and 99% for cool + 99.99% on reads for RA-GRS (read-access to the secondary endpoint).
  • Typically has an RPO of less than 15 minutes (no SLA).
  • Read access to the secondary is available if the primary region is down with RA-GRS.

Geo-zone-redundant storage (GZRS)

GZRS.PNG

  • Data is synchronously replicated 3 times across 3 availability zones in the primary region, then asynchronously replicated to the secondary paired region (3 more copies) = can sustain node failure within the storage cluster, entire datacenter or availability zone going down or a region-wide outage (only region failure would require account failover to restore read and write availability - https://aka.ms/accountfailover).
  • Provides at least 16 9s of durability and 99.9% of availability (reads & writes) for hot tier and 99% for cool + 99.99% on reads for RA-GRS (read-access to the secondary endpoint).
  • Typically has an RPO of less than 15 minutes (no SLA).
  • Read access to the secondary is available if the primary region is down with RA-GZRS.

Account failover

Account failover.PNG

  • Allows you to initiate the failover at the account level in case of an ongoing/upcoming disaster (certain restrictions apply - account failover considerations).
  • Generally available in all public regions.
  • Failover is disruptive and converts the account to LRS.
  • Typically has an RTO of less 1 hour (no SLA).

Failover timeline.PNGBe aware of potential data loss! Always check LastSyncTime before executing the failover.

 

Hope this helps you get a good grasp of durability and availability options for your storage needs! For more details please refer to our documentation:

We'd love to hear from you - please reach us out via email at azurestoragefeedback@microsoft.com and/or post to Azure storage feedback forum.