Skip to content

Commit ddee501

Browse files
committed
Removed '(preview)' alerts from sections per User Story 359508
1 parent c7fb390 commit ddee501

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/storage/common/storage-failover-customer-managed-unplanned.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,6 @@ Customer-managed (unplanned) failover enables you to fail over your entire geo-r
2323

2424
This article describes what happens during a customer-managed (unplanned) failover and failback at every stage of the process.
2525

26-
[!INCLUDE [updated-for-az](../../../includes/storage-failover-unplanned-hns-preview-include.md)]
27-
2826
## Redundancy management during unplanned failover and failback
2927

3028
> [!TIP]
@@ -36,7 +34,7 @@ During the customer-managed (unplanned) failover process, the Domain Name System
3634

3735
The original and current redundancy configurations are stored within the storage account's properties. This functionality allows you to return to your original configuration when you fail back. For a complete list of resulting redundancy configurations, read [Recovery planning and failover](storage-disaster-recovery-guidance.md#plan-for-failover).
3836

39-
To regain geo-redundancy after a failover, you need to reconfigure your account as GRS.<!--Keep in mind that GZRS isn't a post-failover option because your storage account utilizes LRS after the failover completes.--> After the account is reconfigured for geo-redundancy, Azure immediately begins copying data from the new primary region to the new secondary. If you configure your storage account for read access to the secondary region, that access is available. However, replication from the primary to the secondary region might take some time to complete.
37+
To regain geo-redundancy after a failover, you need to reconfigure your account as GRS. After the account is reconfigured for geo-redundancy, Azure immediately begins copying data from the new primary region to the new secondary. If you configure your storage account for read access to the secondary region, that access is available. However, replication from the primary to the secondary region might take some time to complete.
4038

4139
> [!WARNING]
4240
> After your account is reconfigured for geo-redundancy, it may take a significant amount of time before existing data in the new primary region is fully copied to the new secondary.

0 commit comments

Comments
 (0)