Azure Classroom Series – 26/Aug/2020

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
    1. Create a resource group
    2. Create a Virtual Machine with Windows Image Preview Preview
    3. Navigate the disks tab in virtual machine creation pages Preview
    4. Don’t change any advanced settings which will create a managed disk Preview
    5. Create a vm Preview
  • 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 Preview Preview Preview
  • Explore Disks blade in Azure VM Preview
  • 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 Preview
  • 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. Preview
  • Azure VM size also determines how many data disks can you have Preview
  • How is disk performance measured?
    • Speed of disk is measured with maximum IOPS (input/output operations per second) Preview
  • 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

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

About learningthoughtsadmin