Sonam Rastogi's Blog: Move Azure VM across Cloud Service

I came across a requirement of moving my azure VMs from one cloud service to another in same subscription. I had Azure VMs having same prefix like ‘MyProjectVM(N)’ where N is from 1..N. So here comes my blog providing such solution.

Below is the code to move a VM from one cloud service to another and then we will look later as to how we can reuse this code to move multiple VMs.

Prerequisites

Virtual Network, Affinity Group and Storage Account are already created.

Steps to move one VM

1. Manual Step from Microsoft Azure Portal – Create a New Cloud Service(destination cloud service), if not already exists. Create a TestVM in the new cloud service with required affinity group and virtual network information mentioned while creating. This step is required if you want to associate your destination cloud service with the virtual network. We can delete TestVM once at least one VM is moved to the destination cloud service.

2. Follow Below steps to move VM

a. Declare Variables

#Step 1 : Declare Variables
$CurrentCloudServiceName = "CurrentService"
$NewCloudServiceName = "NewService"
$StorageAccount = "MyProjectStoarge"
$SubscriptionName = "My Project Subscription"
$VMNameToMove = "MyProjectVM1"
$SavedVMStateFilePath = "E:\XML\MyProjectVM1.xml"

b. Set Storage Account

#Step 2 : Set Azure Subscription
Set-AzureSubscription -SubscriptionName $SubscriptionName -CurrentStorageAccountName $StorageAccount
Select-AzureSubscription $SubscriptionName

c. Export VM

#Step 3 : Export VM
Get-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove
Export-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove-path $SavedVMStateFilePath

d. Edit Azure VM Saved State XML File

This step is required to avoid conflicts in PowerShell endpoint public port.

Open XML File saved in step ‘Export-AzureVM’ above. Look for PowerShell Endpoint which ‘5986’ by default. Modify ‘Port””’ number which is the public port information. Keep ‘LocalPort’ as it is. Save file and close it.

<InputEndpoint>
  <LocalPort>5986</LocalPort>
  <Name>PowerShell</Name>
  <Port>61204</Port>
  <Protocol>tcp</Protocol>
  <Vip>**.**.**.***</Vip>
  <EnableDirectServerReturn>false</EnableDirectServerReturn>
</InputEndpoint>

e. Remove Azure VM

   1: #Step 5 : Remove VM
   2: Remove-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove

f. Import Azure VM into new Cloud Service

   1: #Step 6 : Import VM to new Cloud Service
   2: Import-AzureVM -Path $SavedVMStateFilePath | New-AzureVM -ServiceName $NewCloudServiceName

g. Delete TestVM manually from Microsoft Azure Portal.

The full script will look like below:-

#Step 1 : Declare Variables
$CurrentCloudServiceName = "CurrentService"
$NewCloudServiceName = "NewService"
$StorageAccount = "MyProjectStoarge"
$SubscriptionName = "My Project Subscription"
$VMNameToMove = "MyProjectVM1"
$SavedVMStateFilePath = "E:\XML\MyProjectVM1.xml"

#Step 2 : Set Azure Subscription
Set-AzureSubscription -SubscriptionName $SubscriptionName -CurrentStorageAccountName $StorageAccount
Select-AzureSubscription $SubscriptionName

#Step 3 : Export VM
Get-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove
Export-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove -path $SavedVMStateFilePath

#Step 4 : Edit Saved State (Manual Step)

#Step 5 : Remove VM
Remove-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove

#Step 6 : Import VM to new Cloud Service
Import-AzureVM -Path $SavedVMStateFilePath | New-AzureVM -ServiceName $NewCloudServiceName

Code to move multiple VMs

We can modify above script to move multiple VMs with similar names from one cloud service to another cloud service. In my case the VMs were named like MyProjectVM1, MyProjectVM2… The script will look like below:-

#Step 1 : Declare Variables
$CurrentCloudServiceName = "CurrentService"
$NewCloudServiceName = "NewService"
$StorageAccount = "MyProjectStoarge"
$SubscriptionName = "My Project Subscription"
$VMNamePrefix = "MyProjectVM"
$VMCount = 5
$SavedVMStateFilePath = "E:\XML\"

#Step 2 : Set Azure Subscription
Set-AzureSubscription -SubscriptionName $SubscriptionName -CurrentStorageAccountName $StorageAccount
Select-AzureSubscription $SubscriptionName

#Step 3 : Export VMs
for($vmNum = 1; $i -le $VMCount; $vmNum++)
{
    $VMNameToMove = $VMNamePrefix + $vmNum
    $SavedVMStateFilePathFull = $SavedVMStateFilePath + $VMNamePrefix + $vmNum + ".xml"
    Get-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove
    Export-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove -path $SavedVMStateFilePathFull
}

#Step 4 (Manual Step) : Edit Azure VM Saved State XML File - Change PowerShell endpoint Public Port (as different VMs should have different public ports)

#Step 5 : Remove Azure VMs from current cloud service
for($vmNum = 1; $i -le $VMCount; $vmNum++)
{
    $VMNameToMove = $VMNamePrefix + $vmNum
    Remove-AzureVM -ServiceName $CurrentCloudServiceName -Name $VMNameToMove
}

#Step 6 : Import Azure VMs in new cloud service
for($vmNum = 1; $i -le $VMCount; $vmNum++)
{
    $VMNameToMove = $VMNamePrefix + $vmNum
    $SavedVMStateFilePathFull = $SavedVMStateFilePath + $VMNamePrefix + $vmNum + ".xml"
    Import-AzureVM -Path $SavedVMStateFilePathFull | New-AzureVM -ServiceName $NewCloudServiceName
}

Happy Coding!!!

Useful Info (Thanks Davis for this note)

If you get some warning like this “New-AzureVM : BadRequest: The virtual network ID cannot be null or empty.”

Is because you have a Site to Site VPN. You need to add -VNetName cmd like this: (include the ” “)

Import-AzureVM -Path $SavedVMStateFilePath | New-AzureVM -ServiceName $NewCloudServiceName -VNetName “NetAzure”

Sonam Rastogi's Blog

Friday, 2 June 2017

Move Azure VM across Cloud Service

1 comment: