Skip to content

Commit d0ca1bb

Browse files
PRMerger12PRMerger12
authored
Merge pull request #115633 from tamram/tamram-0519
adding failover note to table of redundancy options
2 parents cd243be + c1a0c1e commit d0ca1bb

File tree

1 file changed

+27
-9
lines changed

1 file changed

+27
-9
lines changed

‎articles/storage/common/storage-redundancy.md

Lines changed: 27 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -134,24 +134,42 @@ You can query the value of the **Last Sync Time** property using Azure PowerShel
134134

135135
## Summary of redundancy options
136136

137-
The following table shows how durable and available your data is in a given scenario, depending on which type of redundancy is in effect for your storage account:
137+
The tables in the following sections summarize the redundancy options available for Azure Storage
138138

139-
| Scenario | LRS | ZRS | GRS/RA-GRS | GZRS/RA-GZRS |
139+
### Durability and availability parameters
140+
141+
The following table describes key parameters for each redundancy option:
142+
143+
| Parameter | LRS | ZRS | GRS/RA-GRS | GZRS/RA-GZRS |
140144
| :------------------------------------------------------------------------------------------------------- | :------------------------------ | :------------------------------- | :----------------------------------- | :----------------------------------- |
141-
| A node within a data center becomes unavailable | Yes | Yes | Yes | Yes |
142-
| An entire data center (zonal or non-zonal) becomes unavailable | No | Yes | Yes | Yes |
143-
| A region-wide outage occurs | No | No | Yes | Yes |
144-
| Read access to data in the secondary region if the primary region becomes unavailable | No | No | Yes (with RA-GRS) | Yes (with RA-GZRS) |
145145
| Percent durability of objects over a given year<sup>1</sup> | at least 99.999999999% (11 9's) | at least 99.9999999999% (12 9's) | at least 99.99999999999999% (16 9's) | at least 99.99999999999999% (16 9's) |
146-
| Supported storage account types<sup>2</sup> | GPv2, GPv1, BlockBlobStorage, BlobStorage, FileStorage | GPv2, BlockBlobStorage, FileStorage | GPv2, GPv1, BlobStorage | GPv2 |
147146
| Availability SLA for read requests<sup>1</sup> | At least 99.9% (99% for cool access tier) | At least 99.9% (99% for cool access tier) | At least 99.9% (99% for cool access tier) for GRS<br /><br />At least 99.99% (99.9% for cool access tier) for RA-GRS | At least 99.9% (99% for cool access tier) for GZRS<br /><br />At least 99.99% (99.9% for cool access tier) for RA-GZRS |
148147
| Availability SLA for write requests<sup>1</sup> | At least 99.9% (99% for cool access tier) | At least 99.9% (99% for cool access tier) | At least 99.9% (99% for cool access tier) | At least 99.9% (99% for cool access tier) |
149148

150149
<sup>1</sup> For information about Azure Storage guarantees for durability and availability, see the [Azure Storage SLA](https://azure.microsoft.com/support/legal/sla/storage/).
151150

152-
<sup>2</sup> For information for storage account types, see [Storage account overview](storage-account-overview.md).
151+
### Durability and availability by outage scenario
152+
153+
The following table indicates whether your data is durable and available in a given scenario, depending on which type of redundancy is in effect for your storage account:
154+
155+
| Outage scenario | LRS | ZRS | GRS/RA-GRS | GZRS/RA-GZRS |
156+
| :------------------------------------------------------------------------------------------------------- | :------------------------------ | :------------------------------- | :----------------------------------- | :----------------------------------- |
157+
| A node within a data center becomes unavailable | Yes | Yes | Yes | Yes |
158+
| An entire data center (zonal or non-zonal) becomes unavailable | No | Yes | Yes | Yes |
159+
| A region-wide outage occurs in the primary region | No | No | Yes<sup>1</sup> | Yes<sup>1</sup> |
160+
| Read access to the secondary region is available if the primary region becomes unavailable | No | No | Yes (with RA-GRS) | Yes (with RA-GZRS) |
161+
162+
<sup>1</sup> Account failover is required to restore write availability if the primary region becomes unavailable. For more information, see [Disaster recovery and storage account failover](storage-disaster-recovery-guidance.md).
163+
164+
### Supported storage account types
165+
166+
The following table shows which redundancy options are supported by each type of storage account. For information for storage account types, see [Storage account overview](storage-account-overview.md).
167+
168+
| LRS | ZRS | GRS/RA-GRS | GZRS/RA-GZRS |
169+
| :------------------------------ | :------------------------------- | :----------------------------------- | :----------------------------------- |
170+
| GPv2, GPv1, BlockBlobStorage, BlobStorage, FileStorage | GPv2, BlockBlobStorage, FileStorage | GPv2, GPv1, BlobStorage | GPv2 |
153171

154-
All data for all types of storage accounts is copied according to the redundancy option for the storage account. Objects including block blobs, append blobs, page blobs, queues, tables, and files are copied. Data in all tiers, including the archive tier, is copied. For more information about blob tiers, see [Azure Blob storage: hot, cool, and archive access tiers](../blobs/storage-blob-storage-tiers.md).
172+
All data for all storage accounts is copied according to the redundancy option for the storage account. Objects including block blobs, append blobs, page blobs, queues, tables, and files are copied. Data in all tiers, including the archive tier, is copied. For more information about blob tiers, see [Azure Blob storage: hot, cool, and archive access tiers](../blobs/storage-blob-storage-tiers.md).
155173

156174
For pricing information for each redundancy option, see [Azure Storage pricing](https://azure.microsoft.com/pricing/details/storage/).
157175

0 commit comments

Comments
 (0)