I'm currently using two on-premise file servers in different locations with DFS-N and DFS-R to sync file shares and provide a unified access path. As we're transitioning some resources to the cloud, I'm considering adding an Azure Files share and using it as a target for the existing DFS shares. My goal is to achieve triple redundancy, but I'm curious if there are any potential drawbacks or issues with this setup?
2 Answers
You should definitely check out Azure File Sync. It can effectively replace DFS-R and let you keep using DFS-N to manage your namespace on-premises. It’s a solid approach for integrating your on-prem resources with Azure.
You're on the right path! Start by creating your Azure Files share, then set up an Azure File Sync Cloud Endpoint and install the AFS agent on both your on-prem DFS servers. After that, wait for replication to complete before you can remove DFS-R. This way, Azure Files becomes your main source of truth, and your local servers just act as caches. You might find my video tutorial helpful for the setup!
Thanks for the guidance! I have a .local domain and I wondered if that could complicate things during the setup. We have VMs in Azure that communicate locally, but no AFS yet.