Azure File Sync seamlessly syncs files from Azure file shares to local servers. In this overview video, learn about Azure File Sync, including how it works and the components needed.
- [Instructor] Once we've created file shares within Azure, we can build on that with the Azure File Sync Service. The Azure File Sync Service allows us to seamlessly sync the files from the Azure file share to our on-premise locations using a sync server. In addition to syncing with our on-premises locations, we can also share files to our app service and we can back them up in the Recovery vault. There are several components that make up the Azure File Sync Service, including the Storage Sync Service, a sync group, registered server or servers, and the Azure File Sync agent.
We're going to explore each of these in a little more detail followed by some additional details about the Azure File Sync Service, and we'll start with the Storage Sync Service. This contains the sync groups, and it also contains the registered servers. The Storage Sync Service must be created before a server can be registered, and the Azure file share must be in the same region as the Storage Sync Service. If you are planning on using the Azure Sync Service, then you'll have to plan for this in advance.
Next we have the sync group which contains endpoint, and there are two of them. There's the cloud endpoint, which points to the storage account and file share. The cloud endpoint will also run a detection job every 24 hours, which means it could take up to 24 hours before you start seeing your files sync. The second endpoint is the server endpoint, and that will point to the registered server and the path of the files. It's also within the server endpoint that you can configure cloud tiering, which we'll talk about in a moment.
And NAS storage is not supported in the server endpoint, it must be a mounted volume. Moving on to the registered server, which contains the share to be synced. In order to register a server, the agent has to be installed, and each server can only be registered to one Sync Service at a time. And you can't just use any server as your registered server, it must be at least Windows Server 2012 R2 and later.
I mentioned cloud tiering. When we enable cloud tiering, frequently accessed, or hot files, are cached locally, and the free space that you allot is the amount of space that is reserved on the local system for cached files. You'll want to consider and plan for this if you're planning on using cloud tiering because you'll need enough room on the local system for those cached files. And cloud tiering does not support volumes with data deduplication. I mentioned that we can backup our Azure file shares, and Microsoft does recommend backing up the cloud share instead of the on-premises share.
But if you are going to backup the on-premises server, then cloud tiering should be disabled. And bare metal backups are not supported. And finally, let's spend a moment talking about encryption when it comes to the Azure File Sync Service. Azure File Sync supports BitLocker encryption, Azure Information Protection, Azure Rights Management services, and Active Directory RMS. Azure File Sync does not support NTFS Encrypted File Systems.
As you can see, there are a lot of bits and pieces required to deploy Azure File Sync, but it's really not that hard, as you'll see in the upcoming lessons. The key points are understanding what the Azure File Sync Service can do, and what are the limitations of the service.