![]() If you’re wanting to do this to create copies of your VM instances, to scale out your workload, remember to generalise or sysprep your VM instance prior to Step 1. Again, this is skewed towards managed disk usage, but, can easily be extended to be used with unmanaged disks as well. I’ve gone through this recently and updated it so that it’s as streamlined, for me, as possible. However, mounting direct from Blob can also be done.This blob post outlines the use of managed disks.Create a new VM instance based on the blob.vhd file.Copy the snapshot from snapshot storage location to Blob storage.If you’re frugal with your VM allocation and have the process to manage people and technology correctly, Managed Disks are great. That aside, Managed Disks are a pretty good feature that makes disk and storage account management considerably simpler. Additionally, Premium disks, you’re paying for what you provision no matter if its managed or unmanaged.If you provision a managed disk that is 1Tb in size, but, only you 10Mb, you will be paying for the privilege of the whole 1Tb disk.If you provision an unmanaged disk that is 1Tb in size, but, only uses 100Gb, you are paying for 100Gb of storage costs.The key bit of information though is as follows: Yes, it's a great feature that makes the management of VM disks simpler. Microsoft will be pushing you to you Managed Disks more and more. Sidebar – standard managed disk warningīefore I go on though, I wanted to issue a quick warning about the differences between standard unmanaged and managed disks. There are probably multiple ways to do this, both right and wrong, but, here’s a process that I’ve been using for a while that I’ve recently tweaked to take advantage of new Azure Managed Disks.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |