In addition to providing a global namespace, the filter-driver component of Azure File Sync performs seamless storage tiering. The sync engine initially did not include the concept of global file locking, but global file locking is a highly anticipated feature for AFS. ![]() But as everyone expected, Microsoft has increased this number significantly. The global file share concept is particularly useful for remote and branch office scenarios.Īt the time of launch, Azure File Sync supported five (5) Windows Server instances in a sync group only. The enrolment process includes running an installer on the Windows Server host machine to deploy the Microsoft sync engine software and filter-driver component. Next, you need to enroll one or more Windows Server instances into the Sync Group. ![]() The first step is to create and configure a Sync Group in Azure. This provides a common file server with synchronized directory structure, permissions, and data for a distributed workgroup. In other words, you can have multiple instances of Windows Servers synchronizing their data and permissions to Azure File Services in the cloud. In this post, we provide insights to help you differentiate Azure File Sync and HubStor, and how you can optionally combine the two solutions in your storage transformation strategy.Īzure File Sync (AFS) is an easy way to integrate multiple Windows Servers into a global namespace. For others, it is a choice of HubStor or AFS. At HubStor, we are often asked about AFS. ![]() UPDATE: This post has been updated to provide more details on Azure File Sync (AFS), its strengths gaps, and limitations, and how it compares to HubStor.Īzure File Sync (AFS) was announced at Microsoft Ignite 2017.
0 Comments
Leave a Reply. |