It's imperative that your file and folder structure is how you want it to be long-term, before you begin the migration. If you need to restructure your data, you must do so as a first step, before you continue with this guide, order a Data Box or setup sync. The remainder of the section describes your options. This means setting up several sync groups to cover a set of files completely. You can sync sub paths of a set of files to each their own Azure file share. Each sync group has at least one server location, called a server endpoint and one Azure file share, called the cloud endpoint. You determine what syncs by setting up Azure File Sync sync groups that each determine where a set of files syncs between. NAS (Network Attached Storage) does not work with this migration path. Data Box will be fed from that location and Azure File Sync will also be set up on that location.
With this migration guide, you must continue to use the on-premises direct attached storage (DAS) that contains your files. Phase 1: Determine how many Azure file shares you need If you're returning to this article, use the navigation on the right side of the screen to jump to the migration phase where you left off. The following sections describe the phases of the migration process in detail. Configure Azure File Sync with authoritative upload.
#Box sync multiple folders windows#
A NAS (Network Attached Storage) for instance or a different server.
#Box sync multiple folders 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.
0 kommentar(er)
