In Event Viewer, review the telemetry, operational and diagnostic event logs.If you encounter issues with Azure File Sync on a server, start by completing the following steps: For more information on remove server endpoints, see Remove a server endpoint. That's why we recommend that you don't remove the server endpoint unless you would like to stop using Azure File Sync with this particular folder or have been explicitly instructed to do so by a Microsoft engineer. Tiered files may exist within your server endpoint namespace even if you never had cloud tiering enabled. These issues won't resolve when the server endpoint is recreated. Or it may result in inaccessible files for tiered files that exist within the server endpoint namespace. For more information, see why do tiered files exist outside of the server endpoint namespace for more information. It may result in data loss in the case that tiered files exist outside of the server endpoint namespace. Removing a server endpoint is a destructive operation.
No: removing a server endpoint isn't like rebooting a server! Removing and recreating the server endpoint is almost never an appropriate solution to fixing issues with sync, cloud tiering, or other aspects of Azure File Sync. Should I remove and recreate my server endpoint? I'm having an issue with Azure File Sync on my server (sync, cloud tiering, etc.). To create a new support request, in the Azure portal, on the Help tab, select the Help + support button, and then select New support request.
#Sync checker how to#
We also describe how to collect important logs from the system if a deeper investigation of the issue is required. This article is designed to help you troubleshoot and resolve issues that you might encounter with your Azure File Sync deployment. You can use Azure File Sync to centralize your organization's file shares in Azure Files, while keeping the flexibility, performance, and compatibility of an on-premises file server.
0 kommentar(er)
