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
| V15.2 Release - [KB5013875](https://support.microsoft.com/topic/9159eee2-3d16-4523-ade4-1bac78469280)| 15.2.0.0 | November 21, 2022 | Supported - Agent version will expire on March 19, 2024 |
30
-
| V15.1 Release - [KB5003883](https://support.microsoft.com/topic/45761295-d49a-431e-98ec-4fb3329b0544)| 15.1.0.0 | September 19, 2022 | Supported - Agent version will expire on March 19, 2024 |
31
-
| V15 Release - [KB5003882](https://support.microsoft.com/topic/2f93053f-869b-4782-a832-e3c772a64a2d)| 15.0.0.0 | March 30, 2022 | Supported - Agent version will expire on March 19, 2024 |
32
29
33
30
## Unsupported versions
34
31
35
32
The following Azure File Sync agent versions have expired and are no longer supported:
36
33
37
34
| Milestone | Agent version number | Release date | Status |
| V15 Release | 15.0.0.0 - 15.2.0.0 | N/A | Not Supported - Agent versions expired on March 19, 2024 |
39
37
| V14 Release | 14.0.0.0 | N/A | Not Supported - Agent versions expired on February 8, 2024 |
40
38
| V13 Release | 13.0.0.0 | N/A | Not Supported - Agent versions expired on August 8, 2022 |
41
39
| V12 Release | 12.0.0.0 - 12.1.0.0 | N/A | Not Supported - Agent versions expired on May 23, 2022 |
@@ -318,147 +316,3 @@ The following items don't sync, but the rest of the system continues to operate
318
316
319
317
- 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.
320
318
- 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.
321
-
322
-
## Version 15.2.0.0
323
-
324
-
The following release notes are for Azure File Sync version 15.2.0.0 (released November 21, 2022). This release contains improvements for the Azure File Sync agent. These notes are in addition to the release notes listed for version 15.0.0.0.
325
-
326
-
### Improvements and issues that are fixed
327
-
328
-
- Fixed a cloud tiering issue in the v15.1 agent that caused the following symptoms:
329
-
- Memory usage is higher after upgrading to v15.1.
330
-
- Storage Sync Agent (FileSyncSvc) service intermittently crashes.
331
-
- Files are failing to recall with error ERROR_INVALID_HANDLE (0x00000006).
332
-
- Fixed a health reporting issue with servers configured to use a non-Gregorian calendar.
333
-
334
-
## Version 15.1.0.0
335
-
336
-
The following release notes are for Azure File Sync version 15.2.0.0 (released September 19, 2022). This release contains improvements for the Azure File Sync agent. These notes are in addition to the release notes listed for version 15.0.0.0.
337
-
338
-
### Improvements and issues that are fixed
339
-
340
-
- Low disk space mode to prevent running out of disk space when using cloud tiering.
341
-
- Low disk space mode is designed to handle volumes with low free space more effectively. On a server endpoint with cloud tiering enabled, if the free space on the volume reaches below a threshold, Azure File Sync considers the volume to be in Low disk space mode.
342
-
343
-
In this mode, Azure File Sync does two things to free up space on the volume:
344
-
345
-
- Files are tiered to the Azure file share more proactively.
346
-
- Tiered files accessed by the user will not be persisted to the disk.
347
-
348
-
To learn more, see the [low disk space mode](file-sync-cloud-tiering-overview.md#low-disk-space-mode) section in the Cloud tiering overview documentation.
349
-
350
-
- Fixed a cloud tiering issue that caused high CPU usage after v15.0 agent is installed.
351
-
352
-
- Miscellaneous reliability and telemetry improvements.
353
-
354
-
## Version 15.0.0.0
355
-
356
-
The following release notes are for Azure File Sync version 15.0.0.0 (released March 30, 2022). This release contains improvements for the Azure File Sync service and agent.
357
-
358
-
### Improvements and issues that are fixed
359
-
360
-
- Reduced transactions when cloud change enumeration job runs
361
-
- Azure File Sync has a cloud change enumeration job that runs every 24 hours to detect changes made directly in the Azure file share and sync those changes to servers in your sync groups. In the v14 release, we made improvements to reduce the number of transactions when this job runs, and in the v15 release we made further improvements. The transaction cost is also more predictable, as each job will now produce one List transaction per directory, per day.
362
-
363
-
- View Cloud Tiering status for a server endpoint or volume
364
-
- The `Get-StorageSyncCloudTieringStatus` cmdlet will show cloud tiering status for a specific server endpoint or for a specific volume (depending on path specified). The cmdlet will show current policies, current distribution of tiered versus fully downloaded data, and last tiering session statistics if the server endpoint path is specified. If the volume path is specified, it will show the effective volume free space policy, the server endpoints located on that volume, and whether these server endpoints have cloud tiering enabled.
365
-
366
-
To get the cloud tiering status for a server endpoint or volume, run the following PowerShell commands:
- The `Debug-StorageSyncServer` cmdlet will diagnose common issues like certificate misconfiguration and incorrect server time. Also, we've simplified Azure File Sync troubleshooting by merging the functionality of some of existing scripts and cmdlets (AFSDiag.ps1, FileSyncErrorsReport.ps1, Test-StorageSyncNetworkConnectivity) into the `Debug-StorageSyncServer` cmdlet.
375
-
376
-
To run diagnostics on the server, run the following PowerShell commands:
- Reliability and telemetry improvements for cloud tiering and sync.
406
-
407
-
### Evaluation Tool
408
-
409
-
Before deploying Azure File Sync, you should evaluate whether it's 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.
410
-
411
-
### Agent installation and server configuration
412
-
413
-
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).
414
-
415
-
- The agent installation package must be installed with elevated (admin) permissions.
416
-
- The agent isn't supported on Nano Server deployment option.
417
-
- The agent is supported only on Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2022.
418
-
- 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.
419
-
- The Storage Sync Agent (FileSyncSvc) service doesn't support server endpoints located on a volume that has the system volume information (SVI) directory compressed. This configuration will lead to unexpected results.
420
-
421
-
### Interoperability
422
-
423
-
- 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](/troubleshoot/azure/azure-storage/file-sync-troubleshoot?toc=/azure/storage/file-sync/toc.json).
424
-
- File Server Resource Manager (FSRM) file screens can cause endless sync failures when files are blocked because of the file screen.
425
-
- Running sysprep on a server that has the Azure File Sync agent installed isn't 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.
426
-
427
-
### Sync limitations
428
-
429
-
The following items don't sync, but the rest of the system continues to operate normally:
430
-
431
-
- Files with unsupported characters. See [Troubleshooting guide](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#handling-unsupported-characters) for a list of unsupported characters.
432
-
- Files or directories that end with a period.
433
-
- Paths that are longer than 2,048 characters.
434
-
- The system access control list (SACL) portion of a security descriptor that's used for auditing.
435
-
- Extended attributes.
436
-
- Alternate data streams.
437
-
- Reparse points.
438
-
- Hard links.
439
-
- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
440
-
- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data.
441
-
442
-
> [!NOTE]
443
-
> Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
444
-
445
-
### Server endpoint
446
-
447
-
- 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.
448
-
- Cloud tiering isn't supported on the system volume. To create a server endpoint on the system volume, disable cloud tiering when creating the server endpoint.
449
-
- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
450
-
- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
451
-
- Don't store an OS or application paging file within a server endpoint location.
452
-
453
-
### Cloud endpoint
454
-
455
-
- 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.
456
-
- 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](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#troubleshoot-rbac)).
457
-
458
-
> [!NOTE]
459
-
> 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.
460
-
461
-
### Cloud tiering
462
-
463
-
- 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.
464
-
- 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