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
| V12 Release | 12.0.0.0 - 12.1.0.0 | N/A | Not Supported - Agent versions expired on May 23, 2022 |
35
34
| V11 Release | 11.1.0.0 - 11.3.0.0 | N/A | Not Supported - Agent versions expired on March 28, 2022 |
36
35
| V10 Release | 10.0.0.0 - 10.1.0.0 | N/A | Not Supported - Agent versions expired on June 28, 2021 |
37
36
| V9 Release | 9.0.0.0 - 9.1.0.0 | N/A | Not Supported - Agent versions expired on February 16, 2021 |
@@ -313,95 +312,3 @@ The following items don't sync, but the rest of the system continues to operate
313
312
### Cloud tiering
314
313
- 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.
315
314
- 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.
316
-
317
-
## Agent version 12.1.0.0
318
-
The following release notes are for version 12.1.0.0 of the Azure File Sync agent released May 20, 2021. These notes are in addition to the release notes listed for version 12.0.0.0.
319
-
320
-
### Improvements and issues that are fixed
321
-
The v12.0 agent release had two bugs which are fixed in this release:
322
-
- Agent auto-update fails to update the agent to a later version.
323
-
- FileSyncErrorsReport.ps1 script does not provide the list of per-item errors.
324
-
325
-
## Agent version 12.0.0.0
326
-
The following release notes are for version 12.0.0.0 of the Azure File Sync agent (released March 26, 2021).
327
-
328
-
### Improvements and issues that are fixed
329
-
- New portal experience to configure network access policy and private endpoint connections
330
-
- You can now use the portal to disable access to the Storage Sync Service public endpoint and to approve, reject and remove private endpoint connections. To configure the network access policy and private endpoint connections, open the Storage Sync Service portal, go to the Settings section and click Network.
331
-
332
-
- Cloud Tiering support for volume cluster sizes larger than 64KiB
333
-
- Cloud Tiering now supports volume cluster sizes up to 2MiB on Server 2019. To learn more, see [What is the minimum file size for a file to tier?](./file-sync-choose-cloud-tiering-policies.md#minimum-file-size-for-a-file-to-tier).
334
-
335
-
- Measure bandwidth and latency to Azure File Sync service and storage account
336
-
- The Test-StorageSyncNetworkConnectivity cmdlet can now be used to measure latency and bandwidth to the Azure File Sync service and storage account. Latency to the Azure File Sync service and storage account is measured by default when running the cmdlet. Upload and download bandwidth to the storage account is measured when using the "-MeasureBandwidth" parameter.
337
-
338
-
For example, to measure bandwidth and latency to the Azure File Sync service and storage account, run the following PowerShell commands:
- Improved error messages in the portal when server endpoint creation fails
346
-
- We heard your feedback and have improved the error messages and guidance when server endpoint creation fails.
347
-
348
-
- Miscellaneous performance and reliability improvements
349
-
- Improved change detection performance to detect files that have changed in the Azure file share.
350
-
- Performance improvements for reconciliation sync sessions.
351
-
- Sync improvements to reduce ECS_E_SYNC_METADATA_KNOWLEDGE_SOFT_LIMIT_REACHED and ECS_E_SYNC_METADATA_KNOWLEDGE_LIMIT_REACHED errors.
352
-
- Fixed a bug that causes data corruption if cloud tiering is enabled and tiered files are copied using Robocopy with the /B parameter.
353
-
- Fixed a bug that can cause files to fail to tier on Server 2019 if Data Deduplication is enabled on the volume.
354
-
- Fixed a bug that can cause AFSDiag to fail to compress files if a file is larger than 2GiB.
355
-
356
-
### Evaluation Tool
357
-
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](file-sync-planning.md#evaluation-cmdlet) section in the planning guide.
358
-
359
-
### Agent installation and server configuration
360
-
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](file-sync-planning.md) and [How to deploy Azure File Sync](file-sync-deployment-guide.md).
361
-
362
-
- A restart is required for servers that have an existing Azure File Sync agent installation.
363
-
- The agent installation package must be installed with elevated (admin) permissions.
364
-
- The agent is not supported on Nano Server deployment option.
365
-
- The agent is supported only on Windows Server 2019, Windows Server 2016, and Windows Server 2012 R2.
366
-
- 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. See [Recommended system resources](file-sync-planning.md#recommended-system-resources) for more information.
367
-
- 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.
368
-
369
-
### Interoperability
370
-
- 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](file-sync-troubleshoot.md).
371
-
- File Server Resource Manager (FSRM) file screens can cause endless sync failures when files are blocked because of the file screen.
372
-
- 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.
373
-
374
-
### Sync limitations
375
-
The following items don't sync, but the rest of the system continues to operate normally:
376
-
- Files with unsupported characters. See [Troubleshooting guide](file-sync-troubleshoot.md#handling-unsupported-characters) for list of unsupported characters.
377
-
- Files or directories that end with a period.
378
-
- Paths that are longer than 2,048 characters.
379
-
- The system access control list (SACL) portion of a security descriptor that's used for auditing.
380
-
- Extended attributes.
381
-
- Alternate data streams.
382
-
- Reparse points.
383
-
- Hard links.
384
-
- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
385
-
- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data.
386
-
387
-
> [!Note]
388
-
> Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
389
-
390
-
### Server endpoint
391
-
- 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.
392
-
- 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.
393
-
- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
394
-
- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
395
-
- Do not store an OS or application paging file within a server endpoint location.
396
-
- The server name in the portal is not updated if the server is renamed.
397
-
398
-
### Cloud endpoint
399
-
- 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](/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.
400
-
- The storage sync service and/or storage account can be moved to a different resource group, subscription, or Azure AD tenant. After the storage sync service or storage account is moved, you need to give the Microsoft.StorageSync application access to the storage account (see [Ensure Azure File Sync has access to the storage account](file-sync-troubleshoot.md?tabs=portal1%252cportal#troubleshoot-rbac)).
401
-
402
-
> [!Note]
403
-
> 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.
404
-
405
-
### Cloud tiering
406
-
- 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.
407
-
- 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.
0 commit comments