Share via

Convert Existing Windows File Server to Azure File Sync

Robin H 20 Reputation points
2024-05-28T21:07:27.88+00:00

Hello -

We're investigating converting a Windows 2008 file server to Azure File with sync/cache server. Reading a number of online documents/forums, the process for setting up Azure File and the sync process looks fairly straightforward.

What we're a bit stumped on is the caching server concept. It seems, in an ideal situation, you'd use your existing file server as the caching server (assuming it meets the necessary requirements). So far, I haven't found any docs or forums that seem to address these specific questions/situations.

Obviously, with ours being Windows 2008, it does not so we would need to address that first, right, by either upgrading the existing server or using Storage Migration to a new server. That all makes sense and would be relatively painless.

But, if we do that - either upgrade or Storage Migration - and then sync, do we still need the same storage (size, number of disks) on what now becomes the caching server? Or, can that be trimmed down significantly (either thru shrinking or removing)? It seems redundant to pay for VM disks AND Azure File space (of the same size).

Assuming we can shrink the VM storage, are there guidelines for how much storage should be allocated, whether than can be a single drive, etc.?

Or, alternatively, could we build a new caching server, sync it with Azure file and then manually move our data into Azure File (via powershell, robocopy, etc.)?

Thanks for any advice, links, etc. that you can provide.

Robin

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,323 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,366 questions
0 comments
Accepted answer
  1. Anand Prakash Yadav 7,805 Reputation points Microsoft Vendor
    2024-05-29T08:02:50.2966667+00:00

    Hello Robin H,

    Thank you for posting your query here! Let’s explore the considerations and options for setting up an Azure File Sync caching server based on your existing Windows 2008 file server.

    Azure File Sync Overview:

    Azure File Sync allows you to centralize your organization’s file shares in Azure Files while maintaining the flexibility, performance, and compatibility of an on-premises file server.

    It transforms an on-premises (or cloud) Windows Server into a quick cache of your Azure file share.

    Server Requirements:

    To set up Azure File Sync, you’ll need a server (either physical or virtual) that meets the following requirements:

    At least one CPU.

    A minimum of 2 GiB of memory.

    A locally attached volume formatted with the NTFS file system.

    Since your existing Windows 2008 file server doesn’t meet these requirements, you’ll need to either upgrade it or migrate to a new server.

    Caching Server Considerations:

    When upgrading or migrating, consider the following:

    Storage Size: The storage size on the caching server doesn’t need to match the original file server exactly. You can trim it down if needed.

    Number of Disks: You can use a single drive or multiple drives, depending on your requirements.

    Azure File Space: Remember that Azure File Sync caches data locally on the server, so you’ll still need sufficient space to store the cached files.

    Redundancy: While it might seem redundant to pay for both VM disks and Azure File space, the caching server provides local access speed and redundancy, which is essential for performance and availability.

    Cost Trade-offs: Balancing cost and performance is crucial. Consider the trade-offs between storage costs and the benefits of having a local cache.

    Guidelines for Allocating Storage:

    There’s no fixed rule for how much storage to allocate, as it depends on your workload and data size.

    Consider the following factors:

    Data Volume: Estimate the total data volume you need to sync. This includes both existing data and any anticipated growth.

    Working Set: The working set (frequently accessed files) should fit comfortably within the caching server’s storage.

    Azure File Share Size: The size of your Azure file share also matters. If you have a large Azure file share, ensure your caching server has enough space to accommodate the most frequently accessed files.

    IOPS and Throughput: Consider the IOPS (input/output operations per second) and throughput requirements for your workload.

    Redundancy: If you want to maintain redundancy, allocate additional space for the cache.

    Alternative Approach:

    If you prefer not to use your existing file server as the caching server, you can build a new caching server:

    Set up a new Windows Server (preferably a more recent version).

    Sync it with Azure File Sync.

    Manually move your data from the old file server to Azure File using tools like PowerShell or Robocopy.

    Follow best practices for Azure File Sync, such as syncing between servers in the same Active Directory Forest or with established trust relationships. https://learn.microsoft.com/en-us/azure/storage/files/storage-files-faq

    Also, make sure to regularly monitor and adjust your caching server’s storage based on usage patterns.

    Further reference: https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-planning

    Do let us know if you have any further queries. I’m happy to assist you further.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sina Salam 13,371 Reputation points
    2024-05-28T22:59:52.8+00:00

    Hello Robin H,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you are planning to migrate your Windows Server 2008 file server to Azure Files using Azure File Sync. Also evaluating the feasibility and steps required to use your existing server or a new server as a caching server for Azure Files. You need clarity on storage requirements, the necessity of upgrading the existing server, and best practices for managing and reducing local storage while ensuring efficient sync and cache performance with Azure.

    While focusing on the problem statement, to solve the problem of migrating your Windows Server 2008 file server to Azure Files using Azure File Sync and addressing the caching server requirements, follow these detailed steps:

    • Upgrade your Server 2008 to 2012 R2 or later.
    • Prepare a new server with Windows Server 2012 R2 or later.
    • Install the SMS on both the source (Windows Server 2008) and the destination server.
    • Use SMS to migrate data from the old server to the new server.
    # Basic outline for SMS migration
Invoke-SmsMigration -SourceComputerName "OldServer" -DestinationComputerName "NewServer"
    • Provision Azure File Share by creating an Azure File Share to host your files in the cloud.
    • Deploy Azure File Sync by setting up Azure File Sync to synchronize your on-premises server with the Azure File Share.
    • Configure the Caching Server by setting up and optimize the local cache on the caching server.

    References

    For more reading, step by steps on how to do the above and references, kindly use the below links:

    Also, check out the additional resources available by the right side of this page.

    Accept Answer

    I hope this is helpful! Do not hesitate to let me know if you have any other questions.

    ** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful ** so that others in the community facing similar issues can easily find the solution.

    Best Regards,

    Sina Salam

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.