Skip to content

Commit ffc13d5

Browse files
jeffpatt24khdownie
andauthored
Update articles/storage/files/geo-redundant-storage-for-large-file-shares.md
Co-authored-by: Ken Downie <[email protected]>
1 parent 824ffa1 commit ffc13d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/files/geo-redundant-storage-for-large-file-shares.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ It's important to understand the following about the Last Sync Time property:
180180
This section lists considerations that might impact your ability to fail over to the secondary region.
181181

182182
- Storage account failover will be blocked if a system snapshot doesn't exist in the secondary region.
183-
- Storage account failover will be blocked if the storage account contains more than 100,000 file shares. To failover this storage account, please open a support request.
183+
- Storage account failover will be blocked if the storage account contains more than 100,000 file shares. To failover the storage account, open a support request.
184184
- File handles and leases aren't retained on failover, and clients must unmount and remount the file shares.
185185
- File share quota might change after failover. The file share quota in the secondary region will be based on the quota that was configured when the system snapshot was taken in the primary region.
186186
- Copy operations in progress will be aborted when a failover occurs. When the failover to the secondary region completes, retry the copy operation.

0 commit comments

Comments
 (0)