That is great and makes your life with Azure easier. With this approach you do not have to consider and monitor the storage account limits, because Azure takes care of it. ![]() You will not see the storage accounts anymore, only the disks which belong to the VMs. This lifting is achieved by the fact, that Azure manages the placement of the managed disks in the background to one or more storage accounts. You can read more about them in one of my previous posts. Why are they so important and why you should use them? These questions will be answered in this blog post and I will also provide some more details about managed disks.įirst of all and this is one of the major reasons you should use managed disks, is the lifting of the Azure storage account limitations. Assign the right disk to your VM.Two weeks ago, Microsoft has announced the next milestone for the Azure IaaS platform, managed disks. Once you created the new disk from the snapshot, assign it to the VM (Must be deallocated) Click on swap OS Diskħ. Create from snapshot like in the example image below Select the right snapshot as determined at point 1Ħ. Create the managed disk Click on createĥ. Add a new Managed disk Click on Add to add a manged disk from Azure marketĤ. Determine the snapshot you want to use for restore Ensure your snapshot is availableĢ. If you need to create a snapshot, just go to the disk and click on “Create snapshot” Click on create snapshotġ. You can create a snapshot from an existing disk, even being up and running on a VM. ![]() On a LAB or even a production environment, it can be useful to restore the system with a snapshot if something goes wrong.ĭespite you can use Azure backup or site recovery for this, Azure is offering a simple feature called “Snapshot”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |