This article describes the improvements and issues thatare fixed in the Azure File Sync Agent v7 release that is dated June 2019.Additionally, this article contains installation instructions for the update.
Improvements and issues that are fixed
- Support for larger file share sizes
- With the preview of larger, 100 TiB Azure file shares, we are increasing the support limits for file sync as well. In this first step, Azure File Sync now supports up to 50 million files in a single, syncing namespace. Other existing limits, for example the number of items per directory level, still apply.
- Support for firewall and virtual network setting on storage accounts
- Azure File Sync now supports the firewall and virtual network setting on storage accounts. To configure your deployment to work with the firewall and virtual network setting, see Configure firewall and virtual network settings.
- PowerShell cmdlet to immediately sync files changed in the Azure file share
- To immediately sync files that are changed in the Azure file share, the Invoke-AzStorageSyncChangeDetection PowerShell cmdlet can be used to manually initiate the detection of changes in the Azure file share. This cmdlet is intended for scenarios where some type of automated process is making changes in the Azure file share or the changes are done by an administrator (like moving files and directories into the share). For end user changes, the recommendation is to install the Azure File Sync agent in an IaaS VM and have end users access the file share through the IaaS VM. This way all changes will quickly sync to other agents without the need to use the Invoke-AzStorageSyncChangeDetection cmdlet. To learn more, see the Invoke-AzStorageSyncChangeDetection documentation.
- Improved portal experience if you encounter files that are not syncing
- If you have files that are failing to sync, we now differentiate between transient and persistent errors in the portal. Transient errors usually resolve themselves without the need for admin action. For example, a file that is currently in use will not sync until the file handle is closed. For persistent errors, we now show the number of files impacted by each error. The persistent error count is also displayed in the files not syncing column of all server endpoints in a sync group.
- Improved Azure Backup file-level restore
- Individual files restored using Azure Backup are now detected and synced to the server endpoint faster.
- Improved cloud tiering recall cmdlet reliability
- The cloud tiering recall cmdlet (Invoke-StorageSyncFileRecall) now supports per file retry count and retry delay, similar to robocopy.
- Support for TLS 1.2 only (TLS 1.0 and 1.1 is disabled)
- Azure File Sync now supports using TLS 1.2 only on servers which have TLS 1.0 and 1.1 disabled. Prior to this improvement, server registration would fail if TLS 1.0 and 1.1 was disabled on the server.
- Miscellaneous performance and reliability improvements for sync and cloud tiering
- There are several reliability and performance improvements in this release. Some of them are targeted to make cloud tiering more efficient and Azure File Sync as a whole work better in those situations when you have a bandwidth throttling schedule set.
More information about the Azure File Sync v7 release
- This update is available for Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019 installations
- Azure File Sync agent version 184.108.40.206 or a later version is required to upgrade existing agent installations.
- A restart may be required if files are in use during the update rollup installation.
- The agent version for the v7 release is 220.127.116.11.
How to obtain and install the Azure File Sync Agent
The Azure File Sync v7 release is currently being flighted to servers which are configured to automatically update when a new version becomes available. Once fighting completes, this update will be available on Microsoft Update and Microsoft Download Center. Flighting means that the release is offered to a limited number of servers first and expands to more severs gradually. It may not be offered to your server right away even if it’s configured to automatically update when a new version becomes available. To immediately install the Azure File Sync v7 release, manually download the update from the Microsoft Update Catalog.
Tolearn more about Azure File Sync agent auto-update, see automatic agent lifecycle management.
Toobtain and install the Azure File Sync v7 release,configure your Azure File Sync agent to automatically update when anew version becomes available or manually download theupdate from the Microsoft Update Catalog.
Configureyour Azure File Sync agent to automaticallyupdate when a new version becomes available
- During the Azure File Sync agent installation(version 6.0 or later), select the “Automaticallyupdate when a new version becomes available” setting.
- If the agent is already installed (version 6.0or later), run the following PowerShell commands to configure auto-update:
- Import-Module "C:\ProgramFiles\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"
- Set-StorageSyncAgentAutoUpdate-PolicyMode InstallLatest -Day <day> -Hour <hour>
Manuallydownload and install the Azure File Sync agent update from the Microsoft UpdateCatalog
Go to thefollowing website to manually download this update from the Microsoft UpdateCatalog:
To manuallyinstall the update package, run the following command from an elevated commandprompt:
- msiexec.exe /p packagename.msp REINSTALLMODE=OMUSREINSTALL=StorageSyncAgent,StorageSyncAgentAzureFileSync,StorageSyncAgentGuardFilter,StorageSyncAgentUpdater/qb /l*v KB4490495.log
For example, toinstall the Azure File Sync agent update for Server 2016, run the followingcommand:
- msiexec.exe /pStorageSyncAgent_WS2016_KB4490495.mspREINSTALLMODE=OMUS REINSTALL=StorageSyncAgent,StorageSyncAgentAzureFileSync,StorageSyncAgentGuardFilter,StorageSyncAgentUpdater/qb /l*v KB4490495.log