We have proceeded with the Azure VM’s updates, software updates, configuration changes, and finally we need to roll back those changes. Now that we have created the managed disk, it’s time to use the Swap OS Disk functionality. At the Size, select a disk size at least the same as the source disk. Then select “Source type” Snapshot and select it. To make the snapshot functional, we need to create a Managed Disk resource.Īt the Create managed disk wizard, select the Region that the Snapshot resides. Fill in a name and disk account type (Standard / Premium) and press create.Īt this point I will create a folder at the VM for revision We make checkpoints all the time and we revert to them even in production. Think of it like the Hyper V CheckPoint functionality. Windows Server operating system stays fully consistent, but no one can guarantee the consistency of any databases currently running. Open the Azure VM, go to Disks, select the OS Disk and press “Create Snapshot”. The first step is to create a snapshot from the Virtual Disk. Using the Snapshot option you will have an identical VM, with the same IDs. Beware, if you want to make Azure VM clones, you need to generalize the VM with Sysprep and Capture the VM. The other option is to create a new VIrtual Machine. One is using the “swap OS Disk” functionality, which gives you the ease to swap the Operating System disk with one click.

With snapshots there are two main options to recover the VM. Of course the last line of defence is the Azure Backup, but using the Snapshot you don’t need to wait the whole Backup / Restore times. It’s a fast and efficient way to have a crash-consistent Disk of a Virtual Machine, before performing tasks, updates, configuration changes, application installations, etc. It’s simple to create and can help the administrators in various tasks. Azure Portal | Playing with Disk Snapshotĭisk Snapshot is a powerful tool to manage Azure VMs.

Azure take snapshot of vm