Impact of Azure Infrastructure to Disk Storage
- Disks are local to Azure Regions i.e. Azure VM & Disk should be from the Same Region (Location).
- Now lets try to create a Windows VM and focus on Disk Section
- Create a resource group
- Create a Virtual Machine with Windows Image
- Navigate the disks tab in virtual machine creation pages
- Don’t change any advanced settings which will create a managed disk
- Create a vm
- In the above case
- A Managed disk with Premium SSD (OS Disk) was created
- There were no other data disks
- Wait for the resource to be created and navigate to Azure VM
- Explore Disks blade in Azure VM
- If we recollect while creating vm, we have created one os disk & as discussed yesterday, azure tries to add one temp disk to every vm that gets created. so in this vm there should two disks
- OS Disk
- Temp Disk
- Resized the image size to b2ms
- Look at the disks inside vm
- C-Drive is premium ssd OS disk
- D-Drive is a temporary disk. Size of temporary disk is dependent of vm size which you select.
- Azure VM size also determines how many data disks can you have
- How is disk performance measured?
- Speed of disk is measured with maximum IOPS (input/output operations per second)
- Speed of disk is measured with maximum IOPS (input/output operations per second)
- VM can be shutdown/de-allocated and then billing of vm will stop. You will still be paying for disk when your vm is deallocated
Topics to be explored
- If there is a managed disk how about un-managed
- Performance of Disks