Skip to content

Commit 05ed20b

Browse files
committed
Minor verbiage updates
1 parent ba66955 commit 05ed20b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,9 @@ Under normal circumstances, a client writes data to a storage account in the pri
6363

6464
### The planned failover process (GRS/RA-GRS)
6565

66-
Begin disaster recovery testing by initiating a failover of your storage account to the secondary region. The following steps describe the failover process, and the subsequent image provides illustration:
66+
Begin disaster recovery testing by initiating a failover of your storage account to the secondary region. The following describes steps within the planned failover process, and the subsequent image provides illustration:
6767

68-
1. The original primary region becomes read only.
68+
1. The primary region temporarily loses both read and write access. RA-GRS or RA-GZRS users will continue to have read access to their secondary region.
6969
1. Replication of all data from the primary region to the secondary region completes.
7070
1. DNS entries for storage service endpoints in the secondary region are promoted and become the new primary endpoints for your storage account.
7171

@@ -83,7 +83,7 @@ While in the failover state, perform your disaster recovery testing.
8383

8484
After testing is complete, perform another failover to failback to the original primary region. During the failover process, as shown in the following image:
8585

86-
1. The original primary region becomes read only.
86+
1. The primary region temporarily loses both read and write access. RA-GRS or RA-GZRS users will continue to have read access to their secondary region.
8787
1. All data finishes replicating from the current primary region to the current secondary region.
8888
1. The DNS entries for the storage service endpoints are changed to point back to the region that was the primary before the initial failover was performed.
8989

@@ -103,7 +103,7 @@ Under normal circumstances, a client writes data to a storage account in the pri
103103

104104
### The planned failover process (GZRS/RA-GZRS)
105105

106-
Begin disaster recovery testing by initiating a failover of your storage account to the secondary region. The following steps describe the failover process, and the subsequent image provides illustration:
106+
Begin disaster recovery testing by initiating a failover of your storage account to the secondary region. The following describes steps within the planned failover process, and the subsequent image provides illustration:
107107

108108
1. The current primary region becomes read only.
109109
1. All data finishes replicating from the primary region to the secondary region.

0 commit comments

Comments
 (0)