azure-docs icon indicating copy to clipboard operation
azure-docs copied to clipboard

Azure Storage Account manual migration of replication type from ZRS to GZRS

Open BalUKurowej opened this issue 3 years ago • 2 comments

I need to manually change the replication type to GZRS from ZRS for a storage account, unfortunately I cannot do it via Powershell, and according to documentation it can be done, but only as part of failover. source: https://docs.microsoft.com/en-us/azure/storage/common/redundancy-migration?tabs=portal#change-the-replication-setting

Transition ...from ZRS ...to GZRS/RA-GZRS:

Request a live migration

OR

Use Azure Portal, PowerShell or Azure CLI to change replication settings for failback operations only.

I tried changing my Storage Account test account with replication type Standard_ZRS to Standard_GZRS and end up with invalid sku error: "PS /home/user> Set-AzStorageAccount -ResourceGroupName "rg-test-01" -AccountName "migrationtest01" -SkuName "Standard_GZRS" Set-AzStorageAccount: Request parameter values are invalid: sku."

Is the method I am using incorrect? What worries me is the statement that migration from ZRS to GZRS is only possible in the form of Live Migration unless it is performed as part of failover. https://docs.microsoft.com/en-us/azure/storage/common/redundancy-migration?tabs=portal#change-the-replication-setting "And if you want to move from ZRS to GZRS or RA-GZRS, then you must perform a live migration, unless you are performing a failback operation after failover."

Does anyone have experience of performing such a change and can point me in the right direction? I spoke with Microsoft and I was advised that I should follow instructions for manual migration and was provided with the documentation mentioned above, but it gives me this "Sku" error....

original command from documentation: Set-AzStorageAccount -ResourceGroupName <resource_group> -Name <storage_account> -SkuName


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

BalUKurowej avatar Aug 08 '22 09:08 BalUKurowej

@BalUKurowej

Thank you reaching out to us. We will look into this and will get back to you with possible solution

Sandeg-MSFT avatar Aug 08 '22 11:08 Sandeg-MSFT

@BalUKurowej Apologies for the delay response! Can you please share the Case Number?

SumanthMarigowda avatar Aug 12 '22 07:08 SumanthMarigowda

Thank you for your dedication to our documentation.

We sincerely apologize for the delayed response. After a careful review, we are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.

#please-close

akashdubey-ms avatar Jun 06 '23 04:06 akashdubey-ms

Any News on this? Got the same issue right now

phoehnel avatar Jul 05 '23 16:07 phoehnel

Any News on this? Got the same issue right now

I am looking into this today. Apologies for the delay on this.

jimmart-dev avatar Jul 05 '23 17:07 jimmart-dev