After I installed Azure Storage Sync Agent some files began to be missing and found in ...\DfsrPrivate\ConflictAndDeleted\ folder.

Question

Hi.

I'm using DFS (Distributed File System Replication) to replicate files between two local servers. Several days ago, I've installed Azure Storage Sync Agent to one of the servers and pointed it to the same folder that gets replicated. My hope was to have the files replicated on the two local servers and in Azure Cloud Storage. At first everything seemed to work fine, and I saw the same files in cloud and on local servers.

However, after several hours, some users reported missing files. I've started searching for these files and found them in a hidden folder named "...\DfsrPrivate\ConflictAndDeleted". Any idea what I'm doing wrong? Based on documentation, Azure File Sync should work with DFS. Any help is appreciated.

Thanks

Answer 1

Hello aron transpobus.com,

Thanks for posting your question in the Microsoft Q&A forum.

While Azure File Sync can work alongside DFS, there are some important considerations and best practices to follow:

• Decide whether you can fully replace DFS-R with Azure File Sync. If possible, this is the recommended approach
• If you need to keep both technologies, disable cloud tiering on the volumes where DFS-R is active. ensure that Azure File Sync server endpoints do not overlap with multiple DFS-R locations.
• Review your Azure File Sync configuration to ensure it's properly set up and not conflicting with your DFS-R settings

By carefully managing the interaction between Azure File Sync and DFS-R, you should be able to resolve the conflicts and achieve the desired replication between your local servers and Azure cloud storage. If problems persist, you may need to consider fully migrating to Azure File Sync or seeking additional support from Microsoft.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Answer 2

Azure Storage Sync is designed to synchronize files between on-premises servers and Azure cloud storage. It uses a hub-and-spoke model, where one server (the hub) syncs with Azure, and other servers (the spokes) sync with the hub. Files are tiered, allowing you to keep frequently accessed data locally and less frequently accessed data in Azure.

Azure Storage Sync does not directly depend on the internet connection for local server-to-server synchronization. However, the initial setup and ongoing management require an internet connection to communicate with Azure.

To summarize, Azure Storage Sync can work well for hybrid scenarios, combining local and cloud storage, while DFS-R is ideal for purely on-premises replication.