You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following release notes are for version 10.0.0.0 of the Azure File Sync agent (released April 9, 2020).
44
+
45
+
### Improvements and issues that are fixed
46
+
47
+
- Improved sync progress in the portal
48
+
- With the V10 agent release, the Azure portal will soon begin to show the type of sync session that is running. E.g. initial download, regular download, background recall (fast disaster recovery cases) and similar.
49
+
50
+
- Improved cloud tiering portal experience
51
+
- If you have files that are failing to tier or recall, you can now view the tiering errors in the server endpoint properties.
52
+
- Additional cloud tiering information is available for a server endpoint:
53
+
- Local cache size
54
+
- Cache usage efficiency
55
+
- Cloud tiering policy details: volume size, current free space, or the last accessed time of the oldest file in the local cache.
56
+
- These changes will ship in the Azure portal shortly after the initial V10 agent release.
57
+
58
+
- Support for moving the Storage Sync Service and/or storage account to a different Azure Active Directory (AAD) tenant
59
+
- Azure File Sync now supports moving the Storage Sync Service and/or storage account to a different resource group, subscription or Azure AD tenant.
60
+
61
+
- Evaluation tool now identifies files or directories that end with a period
62
+
- The [Evaluation tool](https://docs.microsoft.com/azure/storage/files/storage-sync-files-planning#evaluation-cmdlet) has been updated to identify files or directories that end with a period. Files or directories that end with a period are not currently supported by Azure File Sync. To use the updated version of the [Evaluation tool](https://docs.microsoft.com/azure/storage/files/storage-sync-files-planning#evaluation-cmdlet), install the latest version of the [Azure PowerShell module](https://docs.microsoft.com/powershell/azure/install-az-ps).
63
+
64
+
- Miscellaneous performance and reliability improvements
65
+
- Change detection on the Azure file share may fail if virtual network (VNET) and firewall rules are configured on the storage account.
66
+
- No longer 2KB security descriptor limit for syncing discretionary access control lists (DACLs).
67
+
- Reduced memory consumption associated with recall.
68
+
- Improved performance when using the [Invoke-AzStorageSyncChangeDetection](https://docs.microsoft.com/powershell/module/az.storagesync/invoke-azstoragesyncchangedetection) cmdlet.
69
+
- Other miscellaneous reliability improvements.
70
+
71
+
### Evaluation Tool
72
+
Before deploying Azure File Sync, you should evaluate whether it is compatible with your system using the Azure File Sync evaluation tool. This tool is an Azure PowerShell cmdlet that checks for potential issues with your file system and dataset, such as unsupported characters or an unsupported OS version. For installation and usage instructions, see [Evaluation Tool](https://docs.microsoft.com/azure/storage/files/storage-sync-files-planning#evaluation-cmdlet) section in the planning guide.
73
+
74
+
### Agent installation and server configuration
75
+
For more information on how to install and configure the Azure File Sync agent with Windows Server, see [Planning for an Azure File Sync deployment](storage-sync-files-planning.md) and [How to deploy Azure File Sync](storage-sync-files-deployment-guide.md).
76
+
77
+
- The agent installation package must be installed with elevated (admin) permissions.
78
+
- The agent is not supported on Nano Server deployment option.
79
+
- The agent is supported only on Windows Server 2019, Windows Server 2016, and Windows Server 2012 R2.
80
+
- The agent requires at least 2 GiB of memory. If the server is running in a virtual machine with dynamic memory enabled, the VM should be configured with a minimum 2048 MiB of memory.
81
+
- The Storage Sync Agent (FileSyncSvc) service does not support server endpoints located on a volume that has the system volume information (SVI) directory compressed. This configuration will lead to unexpected results.
82
+
83
+
### Interoperability
84
+
- Antivirus, backup, and other applications that access tiered files can cause undesirable recall unless they respect the offline attribute and skip reading the content of those files. For more information, see [Troubleshoot Azure File Sync](storage-sync-files-troubleshoot.md).
85
+
- File Server Resource Manager (FSRM) file screens can cause endless sync failures when files are blocked because of the file screen.
86
+
- Running sysprep on a server that has the Azure File Sync agent installed is not supported and can lead to unexpected results. The Azure File Sync agent should be installed after deploying the server image and completing sysprep mini-setup.
87
+
88
+
### Sync limitations
89
+
The following items don't sync, but the rest of the system continues to operate normally:
90
+
- Files with unsupported characters. See [Troubleshooting guide](storage-sync-files-troubleshoot.md#handling-unsupported-characters) for list of unsupported characters.
91
+
- Files or directories that end with a period.
92
+
- Paths that are longer than 2,048 characters.
93
+
- The system access control list (SACL) portion of a security descriptor that's used for auditing.
94
+
- Extended attributes.
95
+
- Alternate data streams.
96
+
- Reparse points.
97
+
- Hard links.
98
+
- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
99
+
- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data.
100
+
101
+
> [!Note]
102
+
> Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
103
+
104
+
### Server endpoint
105
+
- A server endpoint can be created only on an NTFS volume. ReFS, FAT, FAT32, and other file systems aren't currently supported by Azure File Sync.
106
+
- Cloud tiering is not supported on the system volume. To create a server endpoint on the system volume, disable cloud tiering when creating the server endpoint.
107
+
- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
108
+
- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
109
+
- Do not store an OS or application paging file within a server endpoint location.
110
+
- The server name in the portal is not updated if the server is renamed.
111
+
112
+
### Cloud endpoint
113
+
- Azure File Sync supports making changes to the Azure file share directly. However, any changes made on the Azure file share first need to be discovered by an Azure File Sync change detection job. A change detection job is initiated for a cloud endpoint once every 24 hours. To immediately sync files that are changed in the Azure file share, the [Invoke-AzStorageSyncChangeDetection](https://docs.microsoft.com/powershell/module/az.storagesync/invoke-azstoragesyncchangedetection) PowerShell cmdlet can be used to manually initiate the detection of changes in the Azure file share. In addition, changes made to an Azure file share over the REST protocol will not update the SMB last modified time and will not be seen as a change by sync.
114
+
- The storage sync service and/or storage account can be moved to a different resource group or subscription within the existing Azure AD tenant. If the storage account is moved, you need to give the Hybrid File Sync Service access to the storage account (see [Ensure Azure File Sync has access to the storage account](https://docs.microsoft.com/azure/storage/files/storage-sync-files-troubleshoot?tabs=portal1%2Cportal#troubleshoot-rbac)).
115
+
116
+
> [!Note]
117
+
> When creating the cloud endpoint, the storage sync service and storage account must be in the same Azure AD tenant. Once the cloud endpoint is created, the storage sync service and storage account can be moved to different Azure AD tenants.
118
+
119
+
### Cloud tiering
120
+
- If a tiered file is copied to another location by using Robocopy, the resulting file isn't tiered. The offline attribute might be set because Robocopy incorrectly includes that attribute in copy operations.
121
+
- When copying files using robocopy, use the /MIR option to preserve file timestamps. This will ensure older files are tiered sooner than recently accessed files.
122
+
41
123
## Agent version 9.1.0.0
42
124
The following release notes are for version 9.1.0.0 of the Azure File Sync agent released December 12, 2019. These notes are in addition to the release notes listed for version 9.0.0.0.
0 commit comments