Merge pull request #265293 from khdownie/patch-1

Update file-sync-server-endpoint-create.md

Author: prmerger-automator[bot]

articles/storage/file-sync/file-sync-server-endpoint-create.md

@@ -4,21 +4,21 @@ description: Understand the options during server endpoint creation and how to b
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: how-to
-ms.date: 06/01/2021
+ms.date: 02/05/2024
 ms.author: kendownie
 ---
 
 # Create an Azure File Sync server endpoint
 
 A server endpoint represents a specific location on a registered server, such as a folder on a server volume. A server endpoint must meet the following conditions:
 
-- A server endpoint must be a path on a registered server (rather than a mounted share). Network attached storage (NAS) is not supported.
-- Although the server endpoint can be on the system volume, server endpoints on the system volume may not use cloud tiering.
-- Changing the path or drive letter after you established a server endpoint on a volume is not supported. Make sure you are using a suitable path before creating the server endpoint.
+- A server endpoint must be a path on a registered server (rather than a mounted share). Network attached storage (NAS) isn't supported.
+- Although the server endpoint can be on the system volume, server endpoints on the system volume can't use cloud tiering.
+- Changing the path or drive letter after you established a server endpoint on a volume isn't supported. Make sure you're using a suitable path before creating the server endpoint.
 - A registered server can support multiple server endpoints, however, a sync group can only have one server endpoint per registered server at any given time. Other server endpoints within the sync group must be on different registered servers.
-- Multiple server endpoints can exist on the same volume if their namespaces are not overlapping (for example, F:\sync1 and F:\sync2) and each endpoint is syncing to a unique sync group. 
+- Multiple server endpoints can exist on the same volume if their namespaces aren't overlapping (for example, F:\sync1 and F:\sync2) and each endpoint is syncing to a unique sync group. 
 
-This article helps you understand the options and decisions needed to create a new server endpoint and start sync. For this to work, you need to have finished [planning for your Azure File Sync deployment](file-sync-planning.md) and also have deployed [resources needed in prior steps](file-sync-deployment-guide.md) to creating a server endpoint.
+This article helps you understand the options and decisions needed to create a new server endpoint and start sync. For this to work, you need to have finished [planning for your Azure File Sync deployment](file-sync-planning.md) and also have deployed [resources needed in prior steps](file-sync-deployment-guide.md) to create a server endpoint.
 
 ## Prerequisites
 
@@ -68,7 +68,7 @@ A server endpoint can only succeed provisioning with the authoritative upload op
 * New or updated files and folders will be uploaded from the server.
 * Files and folders that don't exist on the server (anymore) will be deleted from the cloud share.
 * Metadata-only changes to files and folders on the server will be efficiently moved to the cloud share as metadata-only updates.
-* Files and folders might exist on server and the cloud share. But some files or folders may have changed their parent directory on the server since the seeding of the Azure file share. These files and folders will be purged from the cloud share and uploaded again. Because of this, it's best to avoid restructuring your namespace at a larger scale during a migration.
+* Files and folders might exist on server and the cloud share. But some files or folders might have changed their parent directory on the server since the seeding of the Azure file share. These files and folders will be purged from the cloud share and uploaded again. Because of this, it's best to avoid restructuring your namespace at a larger scale during a migration.
 
 ### Initial download section
 
@@ -85,22 +85,22 @@ As part of this section, a choice can be made for how content from the Azure fil
     :::column-end:::
     :::column:::
 * **Namespace only** </br> Will bring only the file and folder structure from the Azure file share to the local server. None of the file content is downloaded. This option is the default if you previously enabled cloud tiering for this new server endpoint.
-* **Namespace first, then content** </br> For a faster availability of the data, your namespace is brought down first, independent of your cloud tiering setting. Once the namespace is available on the server, the file content is then recalled from the cloud to the server. Recall happens based on the last-modified timestamp on each file. If there is not enough space on the server volume, the remaining files will remain tiered files. This option is the default if you did not turn on cloud tiering for this server endpoint.
-* **Avoid tiered files** </br> This option will download each file in its entirety before the file shows up in the folder on server. This option avoids a tiered file to ever exist on the server. A namespace item and file content are always present at the same time. Avoid this option if fast disaster recovery from the cloud is your reason for creating a server endpoint. If you have applications that require full files to be present, and cannot tolerate tiered files in their namespace, this is ideal. This option is not available if you are using cloud tiering for your new server endpoint.
+* **Namespace first, then content** </br> For a faster availability of the data, your namespace is brought down first, independent of your cloud tiering setting. Once the namespace is available on the server, the file content is then recalled from the cloud to the server. Recall happens based on the last-modified timestamp on each file. If the free space on server volume is less than 10%, the remaining files will remain tiered files. This option is the default if you didn't turn on cloud tiering for this server endpoint.
+* **Avoid tiered files** </br> This option will download each file in its entirety before the file shows up in the folder on server. This option avoids a tiered file to ever exist on the server. A namespace item and file content are always present at the same time. Avoid this option if fast disaster recovery from the cloud is your reason for creating a server endpoint. If you have applications that require full files to be present and can't tolerate tiered files in their namespace, this is ideal. This option isn't available if you're using cloud tiering for your new server endpoint.
     :::column-end:::
 :::row-end:::
 
-Once you select an initial download option, you cannot change it after you confirm to create the server endpoint. 
+Once you select an initial download option, you can't change it after you confirm to create the server endpoint. 
 
 > [!NOTE]
 > When adding a server endpoint and files exist in the Azure file share, if you choose to download the namespace first, files will show up as tiered until they're downloaded locally. Files are downloaded using a single thread by default to limit network bandwidth usage. To improve the file download performance, use the [Invoke-StorageSyncFileRecall](file-sync-how-to-manage-tiered-files.md#how-to-recall-a-tiered-file-to-disk) cmdlet with a thread count greater than 1.
 
 ### File download behavior once initial download completes
 
-How files appear on the server after initial download finishes, depends on your use of the cloud tiering feature and whether or not you opted to [proactively recall changes in the cloud](file-sync-cloud-tiering-overview.md#proactive-recalling). The latter is a feature useful for sync groups with multiple server endpoints in different geographic locations.
+How files appear on the server after initial download finishes depends on your use of the cloud tiering feature and whether or not you opted to [proactively recall changes in the cloud](file-sync-cloud-tiering-overview.md#proactive-recalling). The latter is a feature useful for sync groups with multiple server endpoints in different geographic locations.
 
 * **Cloud tiering is enabled** </br> New and changed files from other server endpoints will appear as tiered files on this server endpoint. These changes will only come down as full files if you opted for [proactive recall](file-sync-cloud-tiering-overview.md#proactive-recalling) of changes in the Azure file share by other server endpoints.
-*  **Cloud tiering is disabled** </br> New and changed files from other server endpoints will appear as full files on this server endpoint. They will not appear as tiered files first and then recalled. Tiered files with cloud tiering off are a fast disaster recovery feature and appear only during initial provisioning.
+*  **Cloud tiering is disabled** </br> New and changed files from other server endpoints will appear as full files on this server endpoint. They won't appear as tiered files first and then recalled. Tiered files with cloud tiering off are a fast disaster recovery feature and appear only during initial provisioning.
 
 
 ## Next steps