I'm sorry to be the one to tell you this, but I don't think you'll be able to get back your uploaded documents. To avoid this scenario recurring, you'll
need to store your data differently.
The local disk storage of Compute VMs (whether Web Role, Worker Role, or VM Role) is not persistent. It can go away at any time. The data
center has the right to move and re-create your VMs whenever it deems it necessary. This could happen in response to a hardware failure, or simply because the data center needs to be reorganized. When this happens, you lose your VM disk files and go back to
your deployment image. It is only a matter of time before this happens. This is normal behavior for cloud computing compute instances.
How do you keep your data in the cloud persistent? It's best to use a persistent, managed service such as Windows Azure Storage or SQL Azure
database. That gives you storage you can depend on, backed by triple redundancy.
If you are unable to to move to persistent storage, another approach that may work (if the data files are read-only) is to add the data
files to your deployment package and upgrade your VM instances with the package.
David Pallmann GM Application Development, Neudesic Windows Azure MVP
Proposed As Answer bywely_liveMVPMonday, October 03, 2011 2:28 AM
>>>If you are unable to to move to persistent storage, another approach that may work (if the data files are read-only) is to add the data files to your
deployment package and upgrade your VM instances with the package.
I have tried to add folder and files in our web application project and we publish using cloud project.
But the folders and files are not included in deployment package (.scpkg and .cscfg).
Please set "Copy to Output Directory" to true for all those files. But note this approach does not work if you need to let your clients to upload files dynamically. To support that scenario, you have to use Windows Azure storage.
Drive storage will help you to to migrate existing code to Windows Azure, as it allows you to use standard NTFS API to work with files, while upload the
files to blob storage automatically in the background. But note only a single instance can use a writable drive at a time. If you need to let multiple instances write to Azure storage simultanously, you'll have to use blob storage directly.