Skip to content

Commit 9f64333

Browse files
committed
Added all articles (.md) in /storage/blobs
1 parent 1b42492 commit 9f64333

File tree

5 files changed

+11
-12
lines changed

5 files changed

+11
-12
lines changed

articles/storage/.openpublishing.redirection.storage.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,5 @@
11
{
22
"redirections": [
3-
{
4-
"source_path_from_root": "/articles/storage/common/storage-failover-customer-managed-planned.md",
5-
"redirect_url": "/articles/storage/common/storage-failover-customer-managed-unplanned",
6-
"redirect_document_id": false
7-
},
83
{
94
"source_path_from_root": "/articles/storage/common/azure-defender-storage-configure.md",
105
"redirect_url": "/azure/defender-for-cloud/defender-for-storage-introduction",

articles/storage/blobs/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -450,7 +450,9 @@ items:
450450
items:
451451
- name: Disaster recovery planning and failover
452452
href: ../common/storage-disaster-recovery-guidance.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
453-
- name: How customer-managed failover works
453+
- name: How customer-managed planned failover (preview) works
454+
href: ../common/storage-failover-customer-managed-planned.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
455+
- name: How customer-managed (unplanned) failover works
454456
href: ../common/storage-failover-customer-managed-unplanned.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
455457
- name: Initiate account failover
456458
href: ../common/storage-initiate-account-failover.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json

articles/storage/blobs/data-protection-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.reviewer: prishet
1616

1717
Azure Storage provides data protection for Blob Storage and Azure Data Lake Storage Gen2 to help you to prepare for scenarios where you need to recover data that has been deleted or overwritten. It's important to think about how to best protect your data before an incident occurs that could compromise it. This guide can help you decide in advance which data protection features your scenario requires, and how to implement them. If you should need to recover data that has been deleted or overwritten, this overview also provides guidance on how to proceed, based on your scenario.
1818

19-
In the Azure Storage documentation, *data protection* refers to strategies for protecting the storage account and data within it from being deleted or modified, or for restoring data after it has been deleted or modified. Azure Storage also offers options for *disaster recovery*, including multiple levels of redundancy to protect your data from service outages due to hardware problems or natural disasters, and customer-managed failover in the event that the data center in the primary region becomes unavailable. For more information about how your data is protected from service outages, see [Disaster recovery](#disaster-recovery).
19+
In the Azure Storage documentation, *data protection* refers to strategies for protecting the storage account and data within it from being deleted or modified, or for restoring data after it has been deleted or modified. Azure Storage also offers options for *disaster recovery*, including multiple levels of redundancy to protect your data from service outages due to hardware problems or natural disasters. Customer-managed (unplanned) failover is another disaster recovery option that allows you to fail over to a secondary region if the primary region becomes unavailable. For more information about how your data is protected from service outages, see [Disaster recovery](#disaster-recovery).
2020

2121
## Recommendations for basic data protection
2222

@@ -109,9 +109,9 @@ The following table summarizes the cost considerations for the various data prot
109109

110110
Azure Storage always maintains multiple copies of your data so that it's protected from planned and unplanned events, including transient hardware failures, network or power outages, and massive natural disasters. Redundancy ensures that your storage account meets its availability and durability targets even in the face of failures. For more information about how to configure your storage account for high availability, see [Azure Storage redundancy](../common/storage-redundancy.md).
111111

112-
If a failure occurs in a data center, if your storage account is redundant across two geographical regions (geo-redundant), then you have the option to fail over your account from the primary region to the secondary region. For more information, see [Disaster recovery and storage account failover](../common/storage-disaster-recovery-guidance.md).
112+
If your storage account is configured for geo-redundancy, you have the option to initiate an unplanned failover from the primary to the secondary region during a data center failure. For more information, see [Disaster recovery planning and failover](../common/storage-disaster-recovery-guidance.md#customer-managed-unplanned-failover).
113113

114-
Customer-managed failover isn't currently supported for storage accounts with a hierarchical namespace enabled. For more information, see [Blob storage features available in Azure Data Lake Storage Gen2](./storage-feature-support-in-storage-accounts.md).
114+
Customer-managed failover currently supports storage accounts with a hierarchical namespace enabled in preview status only. For more information, see [Disaster recovery planning and failover](../common/storage-disaster-recovery-guidance.md#plan-for-failover).
115115

116116
## Next steps
117117

articles/storage/blobs/secure-file-transfer-protocol-known-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ To learn more, see [SFTP permission model](secure-file-transfer-protocol-support
8080

8181
- Maximum file upload size via the SFTP endpoint is 500 GB.
8282

83-
- Customer-managed account failover is supported at the preview level in select regions. For more information, see [Azure storage disaster recovery planning and failover](../common/storage-disaster-recovery-guidance.md#azure-data-lake-storage-gen2).
83+
- Customer-managed account failover is supported at the preview level in select regions. For more information, see [Azure storage disaster recovery planning and failover](../common/storage-disaster-recovery-guidance.md#hierarchical-namespace-hns).
8484

8585
- To change the storage account's redundancy/replication settings, SFTP must be disabled. SFTP may be re-enabled once the conversion has completed.
8686

articles/storage/blobs/storage-feature-support-in-storage-accounts.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,8 @@ The following table describes whether a feature is supported in a standard gener
5555
| [Blobfuse](storage-how-to-mount-container-linux.md) | ✅ | ✅ | ✅ | ✅ |
5656
| [Change feed](storage-blob-change-feed.md) | ✅ |  ⬤ |  ⬤ |  ⬤ |
5757
| [Custom domains](storage-custom-domain-name.md) | ✅ | 🟦 | 🟦 | 🟦 |
58-
| [Customer-managed account failover](../common/storage-disaster-recovery-guidance.md?toc=/azure/storage/blobs/toc.json) | ✅ | 🟦 |  ⬤ | 🟦 |
58+
| [Customer-managed planned failover (preview)](../common/storage-disaster-recovery-guidance.md#customer-managed-planned-failover-preview) | 🟦 | 🟦 |  ⬤ |  🟦 |
59+
| [Customer-managed (unplanned) failover](../common/storage-disaster-recovery-guidance.md#customer-managed-unplanned-failover) | ✅ | 🟦 |  ⬤ |  🟦 |
5960
| [Customer-managed keys with key vault in the same tenant](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | ✅ | ✅ | ✅ | ✅ |
6061
| [Customer-managed keys with key vault in a different tenant (cross-tenant)](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | ✅ | ✅ |  ⬤ |  ⬤ |
6162
| [Customer-provided keys](encryption-customer-provided-keys.md) | ✅ |  ⬤ |  ⬤ |  ⬤ |
@@ -105,7 +106,8 @@ The following table describes whether a feature is supported in a premium block
105106
| [Blobfuse](storage-how-to-mount-container-linux.md) | ✅ | ✅ | ✅ | ✅ |
106107
| [Change feed](storage-blob-change-feed.md) | ✅ |  ⬤ |  ⬤ |  ⬤ |
107108
| [Custom domains](storage-custom-domain-name.md) | ✅ | 🟦 | 🟦 | 🟦 |
108-
| [Customer-managed account failover](../common/storage-disaster-recovery-guidance.md?toc=/azure/storage/blobs/toc.json) |  ⬤ |  ⬤ |  ⬤ |  ⬤ |
109+
| [Customer-managed planned failover](../common/storage-failover-customer-managed-planned.md?toc=/azure/storage/blobs/toc.json) |  ⬤ |  ⬤ |  ⬤ |  ⬤ |
110+
| [Customer-managed unplanned failover](../common/storage-failover-customer-managed-unplanned.md?toc=/azure/storage/blobs/toc.json) |  ⬤ |  ⬤ |  ⬤ |  ⬤ |
109111
| [Customer-managed keys with key vault in the same tenant](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | ✅ | ✅ | ✅ | ✅ |
110112
| [Customer-managed keys with key vault in a different tenant (cross-tenant)](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | ✅ | ✅ |  ⬤ |  ⬤ |
111113
| [Customer-provided keys](encryption-customer-provided-keys.md) | ✅ |  ⬤ |  ⬤ |  ⬤ |

0 commit comments

Comments
 (0)