locked
Migrating from CloudDrive to Azure Files in Web/Worker Roles RRS feed

  • Question

  • Azure Files is being billed as a better option than CloudDrives for persistent disks in Web/Worker roles but there is little evidence to support this. We are looking for detailed guidance/timelines on migrating away from the now discontinued CloudDrive to Azure Files in Web/Worker roles.

    Our chief concerns are:

    1) Snapshotting. We were able to previously backup/restore VHDs stored as Page Blobs instantly using AzCopy. The same mechanism doesn't exist at the container level for Azure Files, is there an ETA on shapshot capabilities for Azure Files that would allow us to use it safely in production?

    2) Performance. CloudDrive had sophisticated local cache capabilities, how can the same be achieved with Azure Files to ensure that repeat reads don't generate network requests. Where do we set the local cache size for Azure Files?

    3) Managed API. Can we expect a fully-managed API for mounting/unmounting drives on startup without resorting to P/Invoke?

    [1] - http://stackoverflow.com/questions/15249516/performance-of-azure-paas-cloud-drives-vs-iaas-disks

    [2] - http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/27/persisting-connections-to-microsoft-azure-files.aspx


    • Edited by Nariman H Monday, September 29, 2014 8:24 PM
    Monday, September 29, 2014 1:55 AM

Answers

  • hi Nariman,

    >>1) Snapshotting

    As a Azure storage service, Azure file service also could have the LRS and GRS feature. For backup data, base on my understanding, we could not worry about it . Currently AzCopy didn't support copying files between Azure Blobs and Azure Files, as well as between Azure File shares and Reading Azure File data from Geo Redundant Account’s Secondary Region. But we can use client library such as this article(http://blogs.msdn.com/b/windowsazurestorage/archive/2013/12/04/introducing-read-access-geo-replicated-storage-ra-grs-for-windows-azure-storage.aspx ).

    >>2) Performance.

    As a new feature,  file serive Azure Files supports highly parallel IO, so many threads doing concurrent copies results in significantly better performance. Using robocopy with the right thread count provides much higher throughput for the copy, resulting in shorter total time to transfer the data. Please see this articles(http://azure.microsoft.com/blog/2014/07/24/migrating-data-to-microsoft-azure-files/ ). It seems that Azure File didn't support caching content. File shares based on Azure Files can be access from an Azure VM in the same way they access the local disk.

    >>3) Managed API.

    Currently we could use the Storage Client library 4.0 . It supports files and you can write a quick application to upload files into the service. If you have any feedback about Azure file , you can submit feature request on this page ( http://www.mygreatwindowsazureidea.com/forums/34192-windows-azure-feature-voting.) or post back.

    Regards,

    Will


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, September 29, 2014 12:16 PM