You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/common/storage-disaster-recovery-guidance.md
+4-44Lines changed: 4 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: stevenmatthew
7
7
8
8
ms.service: azure-storage
9
9
ms.topic: conceptual
10
-
ms.date: 06/13/2024
10
+
ms.date: 08/05/2024
11
11
ms.author: shaas
12
12
ms.subservice: storage-common-concepts
13
13
ms.custom: references_regions
@@ -93,22 +93,6 @@ The following table summarizes the resulting redundancy configuration at every s
93
93
94
94
### Customer-managed planned failover (preview)
95
95
96
-
> [!IMPORTANT]
97
-
> Customer-managed planned failover is currently in PREVIEW and limited to the following regions:
98
-
>
99
-
> - France Central
100
-
> - France South
101
-
> - India Central
102
-
> - India West
103
-
> - East Asia
104
-
> - Southeast Asia
105
-
>
106
-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
107
-
>
108
-
> To opt in to the preview, see [Set up preview features in Azure subscription](../../azure-resource-manager/management/preview-features.md) and specify `AllowSoftFailover` as the feature name. The provider name for this preview feature is **Microsoft.Storage**.
Planned failover can be utilized in multiple scenarios including planned disaster recovery testing, a proactive approach to large scale disasters, or to recover from non-storage related outages.
113
97
114
98
During the planned failover process, the primary and secondary regions are swapped. The original primary region is demoted and becomes the new secondary region. At the same time, the original secondary region is promoted and becomes the new primary. After the failover completes, users can proceed to access data in the new primary region and administrators can validate their disaster recovery plan. The storage account must be available in both the primary and secondary regions before a planned failover can be initiated.
@@ -117,35 +101,11 @@ Data loss isn't expected during the planned failover and failback process as lon
117
101
118
102
To understand the effect of this type of failover on your users and applications, it's helpful to know what happens during every step of the planned failover and failback processes. For details about how this process works, see [How customer-managed (planned) failover works](storage-failover-customer-managed-planned.md).
119
103
120
-
### Customer-managed (unplanned) failover
121
-
122
-
<!--Although both types of customer-managed failover work in a similar manner, there are primarily two ways in which they differ:
123
-
124
-
- The management of the redundancy configurations within the primary and secondary regions (LRS or ZRS).
125
-
- The status of the geo-redundancy configuration at each stage of the failover and failback process.
126
-
127
-
The following table compares the redundancy state of a storage account after a failover of each type:
128
-
129
-
| Result of failover on... | Customer-managed planned failover (preview) | Customer-managed (unplanned) failover |
| ...the secondary region | The secondary region becomes the new primary | The secondary region becomes the new primary |
132
-
| ...the original primary region | The original primary region becomes the new secondary |The copy of the data in the original primary region is deleted |
133
-
| ...the account redundancy configuration | The storage account is converted to GRS | The storage account is converted to LRS |
134
-
| ...the geo-redundancy configuration | Geo-redundancy is retained | Geo-redundancy is lost |
135
-
136
-
The following table summarizes the resulting redundancy configuration at every stage of the failover and failback process for each type of failover:
| Original <br> configuration | After <br> failover | After re-enabling <br> geo redundancy | After <br> failback | After re-enabling <br> geo redundancy |
<sup>1</sup> Geo-redundancy is lost during unplanned failover and must be manually reconfigured.<br>
148
-
<sup>2</sup> Geo-redundancy is retained during a unplanned failover and doesn't need to be manually reconfigured.-->
108
+
### Customer-managed (unplanned) failover
149
109
150
110
If the data endpoints for the storage services in your storage account become unavailable in the primary region, you can initiate an unplanned failover to the secondary region. After the failover is complete, the secondary region becomes the new primary and users can proceed to access data there.
Copy file name to clipboardExpand all lines: includes/storage-failover-unplanned-hns-preview-include.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ author: stevenmatthew
6
6
ms.service: azure-storage
7
7
ms.subservice: common-concepts
8
8
ms.topic: "include"
9
-
ms.date: 06/12/2024
9
+
ms.date: 08/05/2024
10
10
ms.author: shaas
11
11
ms.custom: "include file", references_regions
12
12
---
13
13
14
14
> [!IMPORTANT]
15
-
> Customer-managed (unplanned) failover for accounts that have a hierarchical namespace (Azure Data Lake Storage Gen2) or SSH File Transfer Protocol (SFTP) is currently in PREVIEW and only supported in the following regions:
15
+
> Customer-managed (unplanned) failover for accounts that have Azure Data Lake Storage Gen2 enabled is currently in PREVIEW and supported in all public GRS regions. Customer-managed (unplanned) failover for accounts that have SSH File Transfer Protocol (SFTP) enabled is currently in PREVIEW and only supported in the following regions:
0 commit comments