I'm looking to resize my Azure VM to a different SKU and want to ensure that I'm following best practices to avoid any downtime. My current plan is as follows: 1. Backup the VM. 2. Deallocate the VM. 3. Change the size to the new SKU. 4. Start it back up. Is this the recommended approach? Also, if something goes wrong and the VM fails to start after resizing, what would be the safest recovery option? Should I just restore from backup, or are there quicker ways to roll back?
5 Answers
Capacity issues might be your biggest headache right now, especially in constrained regions. Make sure to also check if you have the quota for the new SKU available before making any changes.
You can actually just resize the VM, and Azure will take care of the automatic restart for you. It really depends on how critical your server is. If it’s important, it might be wise to take a snapshot just as a precaution before proceeding.
Generally, resizing is pretty straightforward. Just select the new size and hit okay; your server will shut down, deallocate, resize, and start up again. However, just keep in mind issues with temp disk SKU conversions and other compatibility constraints like switching between v5 and v6 SKUs.
For critical VMs, I recommend taking a snapshot of the OS disk before resizing. If everything goes well, you can delete the snapshot later. It's a minor cost for peace of mind, and clients often appreciate the extra safety.
It’s usually simple unless you're moving from a SKU with a temp disk to one without, which requires more steps. But otherwise, it's as easy as it sounds! Just double-check those details.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures