Configure Azure File Sync. Well, if you're coming from the
previous module, and I hope you are,
you know what a server endpoint is. A server endpoint is going to be one or more
physical or virtual file servers in your local environment.
And when you join or register a server to your
storage service and join a sync group,
you provide a local path to the file share. No Universal Naming
Convention paths nor are Network Attached Storage devices
supported. It needs to be a local internal path.
I had mentioned that you can sync individual file
shares, which is the preferred way to go.
You can add volumes to your sync group, but that doesn't support the
tiering, so you wouldn't get the benefit of heatmap that AFS has as one
of its native features. Within its sync group,
you're limited to one registered server per endpoint.
So in all likelihood, although you may very well have just
one storage service in your environment,
you're likely in a common scenario to have a registered server with multiple
file shares, each share syncing to a separate sync group.
And lastly, there is a PowerShell module.
The nouns start with storage sync that allow you to
configure and customize the service.
One PowerShell cmdlet you may want to be aware of is
New‑StorageSyncNetworkLimit. This helps your AFS implementation
be a better citizen in your local data centers.
In other words, you can throttle the amount of bandwidth that AFS uses on a given registered server.