Skip to main content
𝗚𝗹𝗶𝗺𝗽𝘀𝗲 - 𝗔𝘇𝘂𝗿𝗲 𝗱𝗶𝘀𝗸 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲𝘀

Hi Present days, Container based services/applications are growing than applications running from virtual machines.

Even though container services evolving IT apps landscape, we could not boycott VM usage. Azure VM also requires and plays vital role for some scenarios.

In this post, we are going to see just glimpse of azure disks of VM. This post is not about standard vs premium disk use case FYI.

Azure VM can run with OS disk but it is not good practice.

There are three types of disks.

  1. OS disk
  2. Data disk
  3. Ephemeral disk
We need to know when to use what then only we can avoid performance bottleneck.
𝗗𝗮𝘁𝗮 𝗗𝗶𝘀𝗸 - If we install applications as well in OS disk, we could face performance issue. It is best to use OS disk to have OS infos and booting.
The benefilt of Data disk is
  1. Easy maintanence
  2. Backup and disaster recovery
  3. Performance isolation (as it is far from OS activities) etc.,
𝗘𝗽𝗵𝗲𝗺𝗲𝗿𝗮𝗹 𝗗𝗶𝘀𝗸 - As we have above 2 disks, why and where can we use this disk?
ⓐ It is temporary disk.
ⓑ Good performance with no extra cost.
ⓒ You can create a VM by using ephemeral OS disks free of cost for storage as well as it is stored in local storage not in Azure storage but it suits for stateless workloads. Data can be lost any time.
ⓓ Useful to have page or swap files, tempdb files

𝗘𝗽𝗵𝗲𝗺𝗲𝗿𝗮𝗹 𝗗𝗶𝘀𝗸 𝗡𝗼𝘁𝗲𝘀 ① It is not managed disk.
② It is restricted to use OS and temp disk.
③ It is not being permanent and limited capacity. When VM reboot or other lifecycle event occurs, it can be deleted.

Please add your valuable additional comments, if I missed any. Your comments are welcome.

Comments

Popular posts from this blog

Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...