Skip to main content

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

By
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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

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

By
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
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more