Azure – is it possible to use azure managed disks with azure scale sets, as an OS disk

azure

is it possible to make virtual machine scale set using manged disk.
i am trying this in vmss vm profile but keep getting error

"virtualMachineProfile":{
    "storageProfile":{
        "imageReference":{
            "publisher":"Canonical",
            "offer":"UbuntuServer",
            "sku":"14.04.2-LTS",
            "version":"14.04.2-LTS"
        },
        "osDisk":{
            "osType":"Linux",
            "caching":"ReadWrite",
            "createOption":"FromImage",
            "name":"OSDisk",
            "managedDisk":{
                "storageAccountType":"Premium_LRS"
            }
        },
        "dataDisks": [{
            "lun":0,
            "managedDisk":{
                "id":
                "[resourceId('Microsoft.Compute/disks', 'testvm_OsDisk_1_bac5bcaf20ec4cafbb0f452d631fe68f')]"
            },
            "caching":"None",
            "createOption":"Attach"
        }]
    },
    message ": " Parameter 'osDisk.managedDisk.id' is not allowed.

Best Answer

For now, we can't use managed disk to create Azure VM directly.
But we can create a managed image of managed vm or a snapshot via PowerShell, after that we can use this new image to create azure VM.

$vmName = "myVM" 
$rgName = "myResourceGroup" 
$location = "EastUS" 
$imageName = "myImage"
Stop-AzureRmVM -ResourceGroupName $rgName -Name $vmName -Force
Set-AzureRmVm -ResourceGroupName $rgName -Name $vmName -Generalized
$vm = Get-AzureRmVM -Name $vmName -ResourceGroupName $rgName
$image = New-AzureRmImageConfig -Location $location -SourceVirtualMachineId $vm.ID 
New-AzureRmImage -Image $image -ImageName $imageName -ResourceGroupName $rgName

More information about generalize vm and create image, please refer to this link.

By the way, the comment you added is right, we can use image in this way.

Related Solutions

Azure backup agent cache – Use temprorary disk

Yes you can change the location of cache to a temporary disk (the D drive in Azure VM). Just remember that this disk is not persistent so you can loose data there anytime. To do that, follow those steps to change the cache location:

1- Stop the Backup engine by executing the following command in an elevated command prompt: PS C:> Net stop obengine

2- Do not move the files. Instead, copy the cache space folder to a different drive with sufficient space. The original cache space can be removed after confirming the backups are working with the new cache space

3- Update the following registry entries with the path to the new cache space folder

Registry path : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config Registry Key : ScratchLocation

Value : type your New cache folder location

Registry path : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider

Registry Key : ScratchLocation Value : type your New cache folder location

4- Re-start the Backup engine by executing the following command in an elevated command prompt: PS C:> Net start obengine

Once the backup creation is successfully completed in the new cache location, you can remove the original cache folder.

Azure Disks-Adding disk without stopping it

As we know, we can attach a data disk to Azure VM and there is no need to stop this VM. Here a official article about attach a data disk to Azure Windows VM, please refer to it.

By the way, if you reached the limit of number of disks, we should resize the VM, and this need a reboot.

=========
Update:
Sorry for my mistake, in Azure ASM module we can resize data disk without shutdown VM, but in ARM, we should shutdown this VM and update data disk with powershell, here is the powershell script:

$vm = get-azurermvm -resourcegroup vms -name jasonv
$vm.StorageProfile.DataDisks
Set-AzureRmVMDataDisk -VM $vm -Name jasonv-20170531-143430 -DiskSizeInGB 20
update-azurermvm -vm $vm -ResourceGroupName vms

Best Answer

Related Solutions

Azure backup agent cache – Use temprorary disk

Azure Disks-Adding disk without stopping it

Related Topic