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/redundancy-migration.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,8 @@ There are three ways to change the replication settings:
45
45
46
46
Geo-redundancy and read-access can be changed at the same time. However, any change that also involves zone-redundancy requires a conversion and must be performed separately using a two-step process. These two steps can be performed in any order.
47
47
48
+
For answers to common questions about changing replication types, see the [Storage redundancy change FAQ](storage-redundancy-change-faq.md) article.
49
+
48
50
### Changing redundancy configuration
49
51
50
52
The following table provides an overview of how to switch between replication types.
@@ -351,7 +353,7 @@ Some storage account features aren't compatible with other features or operation
351
353
352
354
Boot diagnostics doesn't support premium storage accounts or zone-redundant storage accounts. When either premium or zone-redundant storage accounts are used for boot diagnostics, users receive a `StorageAccountTypeNotSupported` error upon starting their virtual machine (VM).
353
355
354
-
Any conversion attempts to add zonal redundancy, such as LRS to ZRS or GRS to GZRS, will fail. To convert your account to a zone-redundant SKU, disable boot diagnostics on your account and resubmit the request. To learn more about boot diagnostics, review the [Azure boot diagnostics](/azure/virtual-machines/boot-diagnostics#enable-managed-boot-diagnostics) article.
356
+
Any conversion attempts to add zonal redundancy, such as LRS to ZRS or GRS to GZRS, fail. To convert your account to a zone-redundant SKU, disable boot diagnostics on your account and resubmit the request. To learn more about boot diagnostics, review the [Azure boot diagnostics](/azure/virtual-machines/boot-diagnostics#enable-managed-boot-diagnostics) article.
355
357
356
358
### Storage account type
357
359
@@ -429,7 +431,7 @@ An LRS storage account containing blobs in the archive tier can be switched to G
429
431
430
432
### Protocol support
431
433
432
-
Customer and support initiated conversions are not supported if either of the following cases are true:
434
+
Customer and support initiated conversions aren't supported if either of the following cases are true:
433
435
434
436
- NFSv3 protocol support is enabled for Azure Blob Storage
435
437
- The storage account contains Azure Files NFSv4.1 shares with public endpoint access enabled
@@ -486,6 +488,7 @@ If you remove geo-redundancy (change from GRS to LRS), there's no cost for makin
0 commit comments