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 8.0.0.0 of the Azure File Sync agent (released October 8, 2019).
46
+
47
+
### Improvements and issues that are fixed
48
+
49
+
- Restore performance Improvements
50
+
- Faster recovery times for recovery done through Azure Backup. Restored files will sync back down to Azure File Sync servers much faster.
51
+
- Improved cloud tiering portal experience
52
+
- If you have tiered files that are failing to recall, you can now view the recall errors in the server endpoint properties. Also, the server endpoint health will now show an error and mitigation steps if the cloud tiering filter driver is not loaded on the server.
53
+
- Simpler agent installation
54
+
- The Az\AzureRM PowerShell module is no longer required to register the server making installation simpler and fast.
55
+
- Miscellaneous performance and reliability improvements
56
+
57
+
### Evaluation Tool
58
+
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.
59
+
60
+
### Agent installation and server configuration
61
+
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).
62
+
63
+
- The agent installation package must be installed with elevated (admin) permissions.
64
+
- The agent is not supported on Nano Server deployment option.
65
+
- The agent is supported only on Windows Server 2019, Windows Server 2016, and Windows Server 2012 R2.
66
+
- 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.
67
+
- 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.
68
+
69
+
### Interoperability
70
+
- 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).
71
+
- File Server Resource Manager (FSRM) file screens can cause endless sync failures when files are blocked because of the file screen.
72
+
- 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.
73
+
74
+
### Sync limitations
75
+
The following items don't sync, but the rest of the system continues to operate normally:
76
+
- Files with unsupported characters. See [Troubleshooting guide](storage-sync-files-troubleshoot.md#handling-unsupported-characters) for list of unsupported characters.
77
+
- Files or directories that end with a period.
78
+
- Paths that are longer than 2,048 characters.
79
+
- The discretionary access control list (DACL) portion of a security descriptor if it's larger than 2 KB. (This issue applies only when you have more than about 40 access control entries (ACEs) on a single item.)
80
+
- The system access control list (SACL) portion of a security descriptor that's used for auditing.
81
+
- Extended attributes.
82
+
- Alternate data streams.
83
+
- Reparse points.
84
+
- Hard links.
85
+
- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
86
+
- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data.
87
+
88
+
> [!Note]
89
+
> Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
90
+
91
+
### Server endpoint
92
+
- 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.
93
+
- Tiered files will become inaccessible if the files are not recalled prior to deleting the server endpoint. To restore access to the files, recreate the server endpoint. If 30 days have passed since the server endpoint was deleted or if the cloud endpoint was deleted, tiered files that were not recalled will be unusable. To learn more, see [Tiered files are not accessible on the server after deleting a server endpoint](https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-troubleshoot?tabs=portal1%2Cazure-portal#tiered-files-are-not-accessible-on-the-server-after-deleting-a-server-endpoint).
94
+
- 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.
95
+
- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
96
+
- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
97
+
- Do not store an OS or application paging file within a server endpoint location.
98
+
- The server name in the portal is not updated if the server is renamed.
99
+
100
+
### Cloud endpoint
101
+
- 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.
102
+
- 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)).
103
+
104
+
> [!Note]
105
+
> Azure File Sync does not support moving the subscription to a different Azure AD tenant.
106
+
107
+
### Cloud tiering
108
+
- 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.
109
+
- 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.
110
+
43
111
## Agent version 7.2.0.0
44
112
The following release notes are for version 7.2.0.0 of the Azure File Sync agent released July 24, 2019. These notes are in addition to the release notes listed for version 7.0.0.0.
45
113
@@ -73,7 +141,7 @@ The following release notes are for version 7.0.0.0 of the Azure File Sync agent
73
141
- Improved Azure Backup file-level restore
74
142
- Individual files restored using Azure Backup are now detected and synced to the server endpoint faster.
- The cloud tiering recall cmdlet (Invoke-StorageSyncFileRecall) now supports per file retry count and retry delay, similar to robocopy.
144
+
- The Invoke-StorageSyncFileRecall cmdlet now allows customers to specify per file retry count and per file retry delay similar to robocopy. Previously, this cmdlet would recall all tiered files under a given path in random order. With the new -Order parameter, this cmdlet will recall the hottest data first and honor the cloud tiering policy (stop recalling if the date policy is met or the volume free space is met; whichever happens first).
77
145
- Support for TLS 1.2 only (TLS 1.0 and 1.1 is disabled)
78
146
- Azure File Sync now supports using TLS 1.2 only on servers that 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.
79
147
- Miscellaneous performance and reliability improvements for sync and cloud tiering
0 commit comments