Azure File Sync - SkippedForStableVersionFailure

Question

Hi,

we are using Azure Filesync with Cloud tiering. But some files can't get tiered. If I tier them manually with "Invoke-StorageSyncCloudTiering" I get following answer:

TieredCount                            : 0 AlreadyTieredCount                     : 0 SkippedForSizeCount                    : 0 SkippedForAgeCount                     : 0 SkippedForUnsupportedReparsePointCount : 0 FailedToTierCount                      : 0 ReclaimedSpaceBytes                    : 0 SkippedForStableVersionFailure         : 1 SkippedForGhostingExclusionCount       : 0

I can't find any information about SkippedForStableVersionFailure.

Does anyone know what I can do?

Thanks!

Steffen

Answer 1

·        Check Sync Status: Verify the sync relationship is healthy via the Azure portal or PowerShell cmdlets.

·        Review Event Logs: Check Windows Event Logs for errors or warnings under Applications and Services Logs > Microsoft > AzureFileSync.

·        Verify File Access and Permissions: Ensure files are accessible and not locked by other processes.

·        Check for Corrupted Files: Replace or delete corrupted files and resync.

·        Network Connectivity: Ensure stable network connection and no firewalls blocking the sync.

·        Update Azure File Sync Agent: Use the latest version of the Azure File Sync agent.

·        Manual Intervention: Remove and re-add the sync relationship for the specific file share or folder if needed.

Answer 2

Hi Steffen Hübner,

Welcome to Microsoft Q&A Forum. Thanks for posting your query here!

I understand that while using Azure FileSync with Cloud tiering, some of the files are not getting tiered and facing error mentioned above.

I would suggest you try the below suggestions:

• Please review your cloud tiering policies and settings to confirm they are properly configured. Ensure that both the volume free space policy and the date policy are appropriately set. Please double-check file size and age limits, and any custom exclusion rules.
• Also, please ensure that the reparse points for the files are intact and not corrupted or missing. These reparse points are crucial for Azure File Sync to properly recognize and manage files for cloud tiering.
• Please check the version of the Azure File Sync agent. Ensure that you are using the latest version. If is not updated, please update it to the latest version, sometimes, updating to the latest version can resolve unexpected issues. Updates may include latest fixes for any such known issues.
• Please try syncing the affected folders again through Azure Portal or PowerShell. Initiating a new synchronization may help address any temporary inconsistencies.
• However, please review the Event Viewer on your server for any related error messages or warnings under Applications and Services\Microsoft\FileSync\Agent. Pay attention to Event IDs 9003, 9016, and 9029, as they can provide more details about tiering activity and potential issues.

For additional information, please refer the following document:

• Troubleshoot Azure File Sync sync health and errors
• Troubleshoot Azure File Sync cloud tiering

I hope this helps!

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