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-failover-customer-managed-planned.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,9 +63,9 @@ Under normal circumstances, a client writes data to a storage account in the pri
63
63
64
64
### The planned failover process (GRS/RA-GRS)
65
65
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:
67
67
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.
69
69
1. Replication of all data from the primary region to the secondary region completes.
70
70
1. DNS entries for storage service endpoints in the secondary region are promoted and become the new primary endpoints for your storage account.
71
71
@@ -83,7 +83,7 @@ While in the failover state, perform your disaster recovery testing.
83
83
84
84
After testing is complete, perform another failover to failback to the original primary region. During the failover process, as shown in the following image:
85
85
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.
87
87
1. All data finishes replicating from the current primary region to the current secondary region.
88
88
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.
89
89
@@ -103,7 +103,7 @@ Under normal circumstances, a client writes data to a storage account in the pri
103
103
104
104
### The planned failover process (GZRS/RA-GZRS)
105
105
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:
107
107
108
108
1. The current primary region becomes read only.
109
109
1. All data finishes replicating from the primary region to the secondary region.
0 commit comments