What should I check before upgrading Azure Storage from GPv1 to GPv2?
Asked by
MellowPine47
I need to migrate an Azure Storage account from GPv1 to GPv2 because GPv1 is deprecated. Before running the migration command from the documentation, are there any tools, prerequisites, or best practices I should follow? The account contains a large amount of blob data, and although the documentation says the data will not be affected, I'd appreciate feedback from anyone who has completed this upgrade, especially at scale.
Answers
I used the portal’s migration option and didn’t run into problems. Blobs, tables, and queues continued working normally, and we did a few checks for possible cost changes beforehand. That said, I’d still validate the impact for your own workload before doing production accounts.
Reply to this answer
If this is a GPv1-to-GPv2 upgrade, it’s an in-place conversion, so you shouldn’t need to copy the blobs into a new storage account. The existing data and endpoints are expected to remain available. I’d still test the process on a non-production account first and take a backup or verify recovery options for anything critical. The main thing to review beforehand is billing: GPv2 uses a different transaction-pricing model and supports Hot, Cool, Cold, and Archive tiers, so costs may change even though the data itself isn’t migrated.
Reply to this answer
The service may eventually handle the transition automatically, but I wouldn’t rely on that without checking the current migration deadline and account status. If the portal or command-line option is available, completing a controlled upgrade ahead of time gives you a chance to review pricing and monitor the account instead of waiting for an automatic change.
Reply to this answer
The biggest practical difference is usually the billing model rather than a functional change. The upgrade itself is generally straightforward, but some workloads can see a significant cost increase under GPv2. Review transaction volume, storage tiers, access patterns, and projected spend before proceeding, then monitor costs after the conversion.
Reply to this answer
Add your answer
Answers are reviewed before publication.
BrightCedar6: That’s encouraging. Has anyone tested the upgrade with a large account or a particularly high request volume? I’m mostly wondering whether the pricing change is more noticeable at scale.