If you have more than 30 shares, mapping an on-premises share 1:1 to an Azure file share is often unnecessary. If you have a small enough number of shares, below 30 for a single Windows Server instance, we recommend a 1:1 mapping. The easiest way to picture this scenario is to envision an on-premises share that maps 1:1 to an Azure file share. You might have more folders on your volumes that you currently share out locally as SMB shares to your users and apps. A single Windows Server instance (or cluster) can sync up to 30 Azure file shares. In this step, you'll determine how many Azure file shares you need. This will decrease positive effects of using Azure Data Box for initial, bulk transport of files to Azure. Avoid any unnecessary, folder restructuring during the migration. 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.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.
0 Comments
Leave a Reply. |