Resizing an Azure Virtual Machine


Q: (from Imtisal)

Is there way we can adjust server to go to another configuration on a set schedule?

We have a client currently configured on A6 server and looks like they have high CPU utilization between the hours of 11am-3pm I was wondering if we can upgrade to A7 during those hours.

Does it require a reboot?

 

A:

“Yes”, you could script the resize using our Azure scheduling service and PowerShell scripts. A quick Bing search on “Azure powershell to change vm size“ resulted in the following link: http://msdn.microsoft.com/en-us/library/dn168976(v=nav.70).aspx

Be aware that if a reboot is required (and it often is) it will be performed. If you are using the Azure console for the VM resize, you will receive a warning before the configuration change is saved, the PowerShell won’t receive that warning.

A: (from Rob)

The answer is that yes is reboot is always required when changing the size of a running VM.  AND the resize may not be immediate.  If you change from say an A1 to an A7, or even from an A6 to A7, your VM may have to move to another Hyper-V host depending on how our hosts are loaded.  Once the move is complete, then the VM will be brought up.

 

SDeming Face   Steve

Comments (2)

  1. Saurabh says:

    If I am running SQL Server, can this be done without any issues?

  2. Jed says:

    Better to Load Balance and use autoscale?

Skip to main content