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
When deciding which redundancy configuration is best for your scenario, consider the tradeoffs between lower costs and higher availability. The factors that help determine which redundancy configuration you should choose include:
@@ -124,9 +138,9 @@ There are two ways to initiate a conversion:
124
138
125
139
Instead of opening a support request, customers in most regions can start a conversion and monitor its progress. This option eliminates potential delays related to creating and managing support requests. For help determining the regions in which customer-initiated conversion is supported, see the [region limitations](#region) article.
126
140
127
-
For standard file shares, customer-initiated conversion can be completed in supported regions using the Azure portal, PowerShell, or the Azure CLI.
141
+
For HDD file shares, customer-initiated conversion can be completed in supported regions using the Azure portal, PowerShell, or the Azure CLI.
128
142
129
-
For premium file shares, customer-initiated conversion is available through PowerShell and Azure CLI. Or you can request a [support-initiated conversion](#support-initiated-conversion).
143
+
For SSD file shares, customer-initiated conversion is available through PowerShell and Azure CLI. Or you can request a [support-initiated conversion](#support-initiated-conversion).
130
144
131
145
After initiation, the conversion could still take up to 72 hours to begin.
132
146
@@ -275,10 +289,6 @@ With a manual migration, you copy the data from your existing storage account to
275
289
For more detailed guidance on how to perform a manual migration, see [Move an Azure Storage account to another region](../common/storage-account-move.md).
276
290
277
291
## Limitations for changing replication types
278
-
279
-
> [!IMPORTANT]
280
-
> 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).
281
-
282
292
Limitations apply to some replication change scenarios depending on:
283
293
284
294
-[Region](#region)
@@ -310,19 +320,16 @@ Some storage account types only support certain redundancy configurations, which
310
320
311
321
The following table lists the redundancy options available for storage account types and whether conversion and manual migration are supported:
312
322
313
-
| Storage account type | Supports LRS | Supports ZRS | Supports conversion<br>(from the Azure portal) | Supports conversion<br>(by support request) | Supports manual migration |
<sup>1</sup> Customer-initiated conversion can be undertaken using [Azure Portal](../common/redundancy-migration.md?tabs=portal#customer-initiated-conversion), [PowerShell](../common/redundancy-migration.md?tabs=powershell#customer-initiated-conversion) or the [Azure CLI](../common/redundancy-migration.md?tabs=azure-cli#customer-initiated-conversion). You can also [open a support request](#support-initiated-conversion).<br />
319
329
320
330
### Protocol support
321
331
322
-
You can't convert storage accounts to zone-redundancy (ZRS or GZRS) if either of the following cases are true:
323
-
324
-
- NFSv3 protocol support is enabled for Azure Blob Storage
325
-
- The storage account contains Azure Files NFSv4.1 shares with public endpoint access enabled
332
+
You can't convert storage accounts to zone-redundancy (ZRS or GZRS) if storage account contains NFS file shares with public endpoint access enabled
326
333
327
334
Converting **NFSv4.1 shares with public endpoints enabled isn't supported**. To change redundancy for NFS shares with public endpoints, follow these steps in order:
0 commit comments