Azure File Sync Agent v15

Question

After Update to Version 15 of Azure FileSync Agent, I tried to find the function Invoke-StorageSyncServerChangeDetection

But is doesn't exist. Any ideas?

Answer 1

@Brian Søgaard Søby Welcome to Microsoft Q&A Forum, Thank you for posting you query here!

The Invoke-AzStorageSyncChangeDetection PowerShell cmdlet can only detect a maximum of 10,000 items. For other limitations, see the Invoke-AzStorageSyncChangeDetection documentation.

Changes made to an Azure file share using REST does not update the SMB last modified time and will not be seen as a change by sync.

Invoke-AzStorageSyncChangeDetection If run with -DirectoryPath or -Path parameters, the command will not detect the following changes in the Azure file share:

Files that are deleted, Files that are moved out of the share, Files that are deleted and created with the same name.
If share-level change detection is invoked, all of these changes will be detected. These changes will also be detected when the scheduled change detection job runs.

Azure File Sync uses the Windows USN journal feature on Windows Server to immediately detect files that were changed and upload them to the Azure file share. If files changed are missed due to journal wrap or other issues, the files will not sync to the Azure file share until the changes are detected. Azure File Sync has a server change enumeration job that runs every 24 hours on the server endpoint path to detect changes that were missed by the USN journal. If you don't want to wait until the next server change enumeration job runs, you can now use the Invoke-StorageSyncServerChangeDetection PowerShell cmdlet to immediately run server change enumeration on a server endpoint path.

To immediately run server change enumeration on a server endpoint path, run the following PowerShell commands:

Import-Module "C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"

Invoke-StorageSyncServerChangeDetection -ServerEndpointPath <path>

Note: By default, the server change enumeration scan will only check the modified timestamp. To perform a deeper check, use the -DeepScan parameter.

Please let me know if the issue still persist, I would like to work closer on this issue.

----------

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.