Azure File Sync namespace download

Leif Johansson 26 Reputation points
2021-01-11T19:36:19.19+00:00

I set up a new server endpoint in Azure File Sync with the option "Recall namespace only". But the namespace download took almost 50 hours.
Why is it so slow? We need an faster disaster recovery solution.
The data in the sync group is only around 6 900 000 objects and 10,8 TB.

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,301 questions
0 comments No comments
{count} vote

3 answers

Sort by: Most helpful
  1. SUNOJ KUMAR YELURU 14,466 Reputation points MVP
    2021-01-12T04:32:13.813+00:00

    @Leif Johansson

    Azure File Sync agent runs on a Windows Server machine that connects to the Azure file shares, the effective sync performance depends upon a number of factors in your infrastructure: Windows Server and the underlying disk configuration, network bandwidth between the server and the Azure storage, file size, total dataset size, and the activity on the dataset. Since Azure File Sync works on the file level, the performance characteristics of an Azure File Sync-based solution is better measured in the number of objects (files and directories) processed per second

    To transfer large numbers of files, we recommend that you use AzCopy

    Check on below url
    Azure File Sync performance metrics

    ----------

    Please don’t forget to "Accept the answer" and up-vote wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

  2. Leif Johansson 26 Reputation points
    2021-01-12T08:23:21.837+00:00

    Hi thanks, but how can I use AzCopy on the tiered files?
    Does the AFS agent understand that?


  3. SUNOJ KUMAR YELURU 14,466 Reputation points MVP
    2021-01-12T15:51:31.837+00:00

    @Leif Johansson

    If you are NTFS permission on the servers then the end user computers should be joined to Azure AD domain in order to have access to the file share on the file server.

    There is a well explained video, please go through this [article.][1]

    When using Azure AD for the authentication only 3 NTFS permission types can be granted:

    Storage File Data SMB Share Reader allows read access in Azure Storage file shares over SMB.

    Storage File Data SMB Share Contributor allows read, write, and delete access in Azure Storage file shares over SMB.

    Storage File Data SMB Share Elevated Contributor allows read, write, delete and modify NTFS permissions in Azure Storage file shares over SMB.

    https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-active-directory-enable#2-assign-access-permissions-to-an-identity

    Azure File Share level is using RBAC access.While for root,directory and file level uses NTFS. Do you have link on how to setup the NTFS permission? Here how to set up permission at folder level on the file share: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-active-directory-domain-service-enable#configure-ntfs-permissions-with-windows-file-explorer

    Azure File Sync service contains Sync Groups each Sync group has a File Share acting as a cloud endpoint and can contains several servers acting as a Server Endpoints (cache) so in this case the end users should access the file shares on the file servers (server endpoints). Remember that Azure File sync and Azure files are related products but with different goals. If you only have a Azure File Share then end users should map be file share directly as any other file share.

    strong text[1]: https://azure.microsoft.com/en-in/blog/preview-of-active-directory-for-authentication-on-azure-file/

    Hope this helps!

    Kindly let us know if the above helps or you need further assistance on this issue.


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.