Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Marj Palmer

My feedback

  1. 143 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for the feedback! This is an issue we are aware of and are actively working to close this gap this year. Please feel free to continue to vote for this item to help us prioritize this effort.


    Will Gries
    Program Manager, Azure Files

    An error occurred while saving the comment
    Marj Palmer commented  · 

    Azure File Sync must fully support synchronization of 100% of ALL valid file and directory names as supported on a Windows Server 2016 file system. Reason is an on-premises backup solution would cause the recall of tiered files, Microsoft recommends using a cloud backup solution to back up the Azure file share. That is only feasible when an enterprise has confidence that 100% of the local Windows file server files/folders are copied up to Azure, and currently that is lacking.

    During testing it was observed the file sync agent was skipping and never successfully copying thousands of files up to Azure which contained a variety of different special characters, all fully supported on Windows Server 2016 file system. We observed warnings such as following in the Event log.

    Log Name: Microsoft-FileSync-Agent/Diagnostic
    Source: Microsoft-FileSync-Agent
    Date: 12/6/2017 10:15:19 AM
    Event ID: 1101
    Task Category: None
    Level: Warning
    User: SYSTEM
    Computer: cxx-vmw-wfs-02.contoso.local
    The File Synchronization service failed to upload a file. File name:\\?\F:\shares\GCG_SYNC\17CO Contoso Creative\17CO-266-LetsGoFartherBrandCampaignExternal\in\img-stock\pilotsFA\700721645.jpg; Sync ID: {3af373af-5583-46a8-9f4a-c0a6adf8e308}; Error: 0x80c80065 - The file has been identified to produce persistent errors during sync. Hence, it is blocked from transfering data until the retry interval is reached.

    Marj Palmer supported this idea  · 

Feedback and Knowledge Base