Merge pull request #131780 from fauhse/dts

StorSimple 8000 series migration route via new DTS service

Author: v-dihans

articles/storage/files/media/storage-files-how-to-create-large-file-share/large-file-shares-advanced-enable.png

@@ -23,12 +23,16 @@ If your HR department (for instance) has a total of 15 shares, you might conside
 
 Azure File Sync supports syncing the root of a volume to an Azure file share. If you sync the root folder, then all subfolders and files will go to the same Azure file share.
 
-Syncing the root of the volume isn't always the best answer. There are benefits in syncing multiple locations. For example, doing so helps keep the number of items lower per sync scope. Setting up Azure File Sync with a lower number of items is not just beneficial for file sync. A lower number of items also benefits scenarios like these:
+Syncing the root of the volume isn't always the best answer. There are benefits in syncing multiple locations. For example, doing so helps keep the number of items lower per sync scope. While we test Azure file shares and Azure File Sync with 100 million items (files and folders) per share, a best practice is to try and keep the number below 20 or 30 million in a single share. Setting up Azure File Sync with a lower number of items is not just beneficial for file sync. A lower number of items also benefits scenarios like these:
 
-* Cloud-side restore from an Azure file share snapshot can be taken as a backup.
+* Initial scan of the cloud content before the namespace can start to appear on an Azure File Sync enabled server can complete faster.
+* Cloud-side restore from an Azure file share snapshot will be faster.
 * Disaster recovery of an on-premises server can speed up significantly.
 * Changes made directly in an Azure file share (outside sync) can be detected and synced faster.
 
+> [!TIP]
+> If you are unsure how many files and folder you have, you can check out the TreeSize tool from JAM Software GmbH.
+
 #### A structured approach to a deployment map
 
 Before you deploy cloud storage in a later step, it's important to create a map between on-premises folders and Azure file shares. This mapping will then inform how many and which Azure File Sync *sync group* resources you'll provision. A sync group ties the Azure file share and the folder on your server together and establishes a sync connection.
@@ -48,14 +52,12 @@ To make the decision about how many Azure file shares you need, review the follo
 >
 > This grouping under a common root has no impact on access to your data. Your ACLs stay as is. You would only need to adjust any share paths (like SMB or NFS shares) you might have on the server folders that you now changed into a common root. Nothing else changes.
 
-Another important aspect of Azure File Sync and a balanced performance and experience is understanding the scale factors for Azure File Sync performance. Obviously, when files are synced over the internet, larger files take more time and bandwidth to sync.
-
 > [!IMPORTANT]
 > The most important scale vector for Azure File Sync is the number of items (files and folders) that need to be synchronized.
 
 Azure File Sync supports syncing up to 100 Million items to a single Azure file share. This limit can be exceeded and only shows what the Azure File Sync team tests on a regular basis.
 
-It's a best practice to keep the number of items per sync scope low. That's an important factor to consider in your mapping of folders to Azure file shares.
+It's a best practice to keep the number of items per sync scope low. That's an important factor to consider in your mapping of folders to Azure file shares. While we test Azure file shares and Azure File Sync with 100 million items (files and folders) per share, a best practice is to try and keep the number below 20 or 30 million in a single share. Split your namespace into multiple shares if you start to exceed these numbers. You can continue to group multiple on-prem shares into the same Azure file share, as long as you stay roughly below these numbers. This will provide you with room to grow.
 
 In your situation, it's possible that a set of folders can logically sync to the same Azure file share (using the new, common root folder approach mentioned earlier). But it might still be better to regroup folders such that they sync to two instead of one Azure file share. You can use this approach to keep the number of files and folders per file share balanced across the server.
 
@@ -68,7 +70,7 @@ In your situation, it's possible that a set of folders can logically sync to the
     :::column:::
         Use a combination of the previous concepts to help determine how many Azure file shares you need, and which parts of your existing data will end up in which Azure file share.
 
-        Create a table that records your thoughts, so you can refer to it in the next step. Staying organized is important, because it can be easy to lose details of your mapping plan when you're provisioning many Azure resources at once. To help you in creating a complete mapping, you can download a Microsoft Excel file as a template.
+        Create a table that records your thoughts, so you can refer to it when needed. Staying organized is important, because it can be easy to lose details of your mapping plan when you're provisioning many Azure resources at once. To help you in creating a complete mapping, you can download a Microsoft Excel file as a template.
 
 [//]: # (HTML appears as the only way to accomplish adding a nested two-column table with working image parsing and text/hyperlink on the same line.)