Migration overviewĪs mentioned in the Azure Files migration overview article, using the correct copy tool and approach is important. The latter requires keeping downtime to a minimum, so that it can fit into or only slightly exceed regular maintenance windows. This migration needs to be done in a way that guarantees the integrity of the production data and availability during the migration. Then use Azure File Sync for a hybrid cloud deployment. The goal is to move the shares that you have on your Linux Samba server to a Windows Server instance.

Premium file shares (FileStorage), LRS/ZRS This article guides you through the planning and execution of such a migration. It does not support sync to and from Linux clients, or a remote Server Message Block (SMB) share, or Network File System (NFS) shares.Īs a result, transforming your file services into a hybrid deployment makes a migration to Windows Server necessary. If your scenario is different, look through the table of migration guides.Īzure File Sync works on Windows Server instances with direct attached storage (DAS). Caching files on-premises: Yes, the final goal is an Azure File Sync deployment.Migration route: Linux Server with SAMBA ⇒ Windows Server 2012R2 or later ⇒ sync with Azure file share(s).Data source: Network Attached Storage (NAS).

Linux file sync software