Skip to main content

Windows Azure Virtual Machine - Where is my data from disk D:

Today we will talk about what kind of disk are available on a virtual machine (VM) on Windows Azure. I decided to write this post after someone asked me why the content of disk D: was lost after a restart. He told me that this is a bug of Azure, but is not.
When you are creating a Windows Azure Virtual Machine you will observe that you have more than one disk attached to it. There are 3 types of disk that can exist on a VM on Azure:
  • OS Disk – drive C:
  • Temporary Storage Disk – drive D:
  • Data disk – drive E:, F:, …
The OS disk contains the operating system. This is VHD that can be attached to the machine and contains the operation system. You can create custom VHD that contains the operating system and all other application that you need. In this moment the maximum size of this disk is around 124GB. If you need more space, you can use the data disks.
Each VM can have one or more data disk attached to it. Each VHD that is attached to the VM can have maximum 1TB and the maximum number of data disks that can be attached to a VM is 20. I thing that there is enough space available for any scenario that we imagine.
The Temporary Storage disk is used to store temporary information. For example if you need to cache different content like pictures or documents. In the case of the restart or if something happens with the machine, all the content of this disk is lost. Because of this you should never store data that need to be persisted on this disk. The scope of this disk is not to persist data.
Usually people tend to use this disk to persistent data because they are looking only on the happy flow, when the machine don’t crash or a restart is happening (and don’t read the MSDN). In the happy flow you can have the sensation that the temporary storage disk (D:) can be used to persist your data. You can see and access your data all the time.
Don’t try to use the OS disk to persist data. The same thing will happen when something goes wrong and the machine restart. Your original VHD image will be attached. Because of this all the changes will be lost.
If you need to persist any kind of information you should use the data disks. The information from this disk will not be lost in the case of a crash. Also, you should know that all the VHD images are stored in the blob storage.
From my perspective, all the information that need to be persisted should be stored in the blob. Why? Because you will need to access this data from more than one location.
In conclusion, we shouldn’t use disk D: (temporary storage disk) to store data that need to be persisted. The best place to store this kind of data is data disks or blobs.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...