Is there a difference between storing files in the Local Storage than storing on the Azure Virtual Machine HD (like d:\ or e:)? From what I am understand, they are the same.
THANKS
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Not sure why you wanted to compare local storage with Azure Virtual Machin’s HDs because local storage is applicable to Web/Worker Role scenarios (PaaS) while virtual machine hard disk is applicable to persistent VM scenarios (IaaS). More apt comparison would be between local storage and Azure drives.
From what I understand, the local storage in Windows Azure is temporary. What that means is that if your role instance goes down and can’t be recovered, anything stored in local storage is gone. Secondly local storage is specific to a role instance and you can’t share this across role instances. Thirdly, maximum size of the local storage is limited by the size of your role instance. For example, if your application is deployed in a “Small” sized VM, the maximum amount of local storage you can have is 229.4 MB (ref: http://msdn.microsoft.com/en-us/library/windowsazure/hh369931.aspx).
Comparing that to Azure Virtual Machine HD, they’re persistent storage backed by Windows Azure Blob Storage. These are saved as Page Blobs in Blob Storage. Because of this fact, you can have up to 1 TB (max. size of a page blob) of storage available to you.
Hope this helps.