Skip to content

Commit 5c7750a

Browse files
committed
Removed 'preview' tag
1 parent 159b5b9 commit 5c7750a

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/storage/common/storage-disaster-recovery-guidance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Each type of failover has a unique set of use cases, corresponding expectations
6666

6767
| Type | Failover Scope | Use case | Expected data loss | Hierarchical Namespace (HNS) supported |
6868
|----------------------------------------|-----------------|----------|--------------------|----------------------------------------|
69-
| Customer-managed planned failover | Storage account | The storage service endpoints for the primary and secondary regions are available, and you want to perform disaster recovery testing. <br></br> The storage service endpoints for the primary region are available, but another service is preventing your workloads from functioning properly.<br><br>To proactively prepare for large-scale disasters, such as a hurricane, that might affect a region. | [No](#anticipate-data-loss-and-inconsistencies) | Yes <br> *(In preview)* |
69+
| Customer-managed planned failover | Storage account | The storage service endpoints for the primary and secondary regions are available, and you want to perform disaster recovery testing. <br></br> The storage service endpoints for the primary region are available, but another service is preventing your workloads from functioning properly.<br><br>To proactively prepare for large-scale disasters, such as a hurricane, that might affect a region. | [No](#anticipate-data-loss-and-inconsistencies) | Yes |
7070
| Customer-managed (unplanned) failover | Storage account | The storage service endpoints for the primary region become unavailable, but the secondary region is available. <br></br> You received an Azure Advisory in which Microsoft advises you to perform a failover operation of storage accounts potentially affected by an outage. | [Yes](#anticipate-data-loss-and-inconsistencies) | Yes |
7171
| Microsoft-managed | Entire region | The primary region becomes unavailable due to a significant disaster, but the secondary region is available. | [Yes](#anticipate-data-loss-and-inconsistencies) | Yes |
7272

@@ -291,5 +291,5 @@ Microsoft also recommends that you design your application to prepare for the po
291291
- [Use geo-redundancy to design highly available applications](geo-redundant-design.md)
292292
- [Tutorial: Build a highly available application with Blob storage](../blobs/storage-create-geo-redundant-storage.md)
293293
- [Azure Storage redundancy](storage-redundancy.md)
294-
- [How customer-managed planned failover (preview) works](storage-failover-customer-managed-planned.md)
294+
- [How customer-managed planned failover works](storage-failover-customer-managed-planned.md)
295295
- [How customer-managed (unplanned) failover works](storage-failover-customer-managed-unplanned.md)

0 commit comments

Comments
 (0)