#Box sync folder location install#

Configure Azure File Sync with authoritative upload.

Deploy one or more Azure Data Box devices to move the data from your Windows Server 2012 R2 or newer.

Deploy storage accounts and file shares.

The migration process consists of several phases. This overview page provides a good starting point for all migration scenarios.

For all other scenarios, check the table of Azure file share migration guides.

Rather check out: Migrate from NAS via Data Box to Azure File Sync or find the best guide for your scenario on the migration overview page.

If that is your scenario, then this isn't the right migration guide for you. You will rather create a new, empty server and use Azure File Sync on that server. A NAS (Network Attached Storage) for instance or a different server.

#Box sync folder location install#

You have data on a source where you will not or cannot install AFS on.If this is your scenario, then this article describes your migration path. In this scenario, you don't want to upload all files and use Data Box instead, then use file sync for ongoing changes. Your data lives on a Windows Server 2012 R2 or newer and you plan to install AFS to that server and sync the original location.There are different migration paths available to you, it's important to follow the right one: Using Azure Data Box is a viable path to move the bulk of the data from your on-premises Windows Server to separate Azure file shares and then, optionally, add Azure File Sync on the original source server. Caching files on-premises: Yes, the final goal is an Azure File Sync deployment that syncs the files from where they are now.Migration route: Windows Server 2012 R2 or newer ⇒ Data Box ⇒ Azure file share ⇒ sync with Windows Server original file location.Data source: Windows Server 2012 R2 or newer where Azure File Sync will be installed and point to the original set of files.