Merge pull request #171517 from kartikshah9/patch-11

Update storage-files-faq.md

Author: PRMerger17

articles/storage/files/storage-files-faq.md

@@ -101,6 +101,26 @@ This article answers common questions about Azure Files features and functionali
 
     Performance will vary based on your environmental settings, configuration, and whether this is an initial sync or an ongoing sync. For more information, see [Azure File Sync performance metrics](storage-files-scale-targets.md#azure-file-sync-performance-metrics)
 
+* <a id="afs-initial-upload"></a>
+  **What is Initial upload of data for Azure File Sync?**
+  
+    **Initial sync of data from Windows Server to Azure File share:**
+    Many Azure File Sync deployments start with an empty Azure file share because all the data is on the Windows Server. In these cases, the initial cloud change enumeration is fast and the majority of time will be spent syncing changes from the Windows Server into the Azure file share(s).
+
+While sync uploads data to the Azure file share, there is no downtime on the local file server, and administrators can setup network limits to restrict the amount of bandwidth used for background data upload.
+
+Initial sync is typically limited by the initial upload rate of 20 files per second per sync group. Customers can estimate the time to upload all their data to Azure using the following formulae to get time in days:
+
+**Time (in days) for uploading files to a sync group = (Number of objects in server endpoint)/(20 * 60 * 60 * 24)**
+
+* <a id="afs-initial-upload-server-restart"></a>
+  **What is the impact if the server is stopped and restarted during initial upload**
+  There is no impact. Azure File Sync will resume from sync once the server is restarted from the point it left off
+
+* <a id="afs-initial-upload-server-changes"></a>
+  **What is the impact if changes are made to the data on the server endpoint during initial upload**
+  There is no impact. Azure File Sync will reconcile the changes made on the server endpoint to ensure the cloud endpoint and server endpoint are in sync
+
 * <a id="afs-conflict-resolution"></a>**If the same file is changed on two servers at approximately the same time, what happens?**  
     Azure File Sync uses a simple conflict-resolution strategy: we keep both changes to files that are changed in two endpoints at the same time. The most recently written change keeps the original file name. The older file (determined by LastWriteTime) has the endpoint name and the conflict number appended to the filename. For server endpoints, the endpoint name is the name of the server. For cloud endpoints, the endpoint name is **Cloud**. The name follows this taxonomy: 
 
@@ -222,6 +242,10 @@ This article answers common questions about Azure Files features and functionali
 
    Azure Files runs on top of the same storage architecture that's used in other storage services in Azure Storage. Azure Files applies the same data compliance policies that are used in other Azure storage services. For more information about Azure Storage data compliance, you can refer to [Azure Storage compliance offerings](../common/storage-compliance-offerings.md), and go to the [Microsoft Trust Center](https://microsoft.com/trustcenter/default.aspx).
 
+* <a id="afs-power-outage"></a>
+  **What is the impact to Azure File Sync if there is a power outage which shuts down the server endpoint**
+  There is no impact. Azure File Sync will reconcile the changes made on the server endpoint to ensure the cloud endpoint and server endpoint are in sync once the server endpoint is back online
+
 * <a id="file-auditing"></a>
 **How can I audit file access and changes in Azure Files?**