FS Agent taking to long

Hi @Egor Skepko ,

The issue might be the DC DB.

Scan completed, ScanType=[DC]

Have you tried different Scan Type?

https://documentation.commvault.com/2023e/expert/file_scan_methods_for_windows_file_system_agent.html

Best Regards,

Sebastien

@Egor Skepko ,

Can you try another type and then change back to Optimize Scan?

Best Regards,

Sebastien

@Egor Skepko ,

Can you change to Change Journal, run a Backup and then change back to Optimize Scan and run a Backup.

https://documentation.commvault.com/2023e/expert/file_scan_methods_for_windows_file_system_agent.html

@Egor Skepko ,

no impact but this type will take longer, this will also reset the DC DB.

So once you change back to Optimize Scan hopefully it will work as expected.

HI @Egor Skepko ,

I checked the log again and investigated:

1984  3848  04/16 02:00:07 4367861 CFind::IsJobQualifiedForRunningTrueUp(135) - TrueUp is enabled via subclient Option [0], TrueUp command line [0], TrueUp reg [0], Incremental after Synthetic Full [1]

1984  291c  04/16 08:30:38 4367861 CFileScanJMProgressReportTask::Execute(55) - Total Scanned items count did not change in last [9060] seconds. Current Count: Folders [14504029] , Files [20155885] , Total [34659914] 

So it's not an issue but an expected feature that syncs up the index with client, and makes sure there is no data mismatch:

https://documentation.commvault.com/2023e/expert/reconciling_backups_of_windows_file_system_subclients.html

Also, please see article below: 

True-up is a special function that validates that the synthetic full is not missing data. Consider that file share backups use modified time to detect changed files, if there is a blimp in the system and that file is unavailable during scan, then it will never be picked up by an incremental or synthetic full ever again. So true-up runs on the first incremental after a synthetic full as extra protection to make sure all files are properly captured. The time it takes is dependent on the number of objects / files to scan across the original source.

Best Regards,

Sebastien

@Egor Skepko ,

As explained, it is not an issue. Did you check the link to our documentation and the key you can add?

Now you logged a case we will check and confirm.

I see you had a case for that exact/similar issue (230210-214) where this was discussed with my colleague.

@Egor Skepko 

I see you had a case for that exact/similar issue (230210-214) where this was discussed with my colleague.

@Egor Skepko 

I was talking about the ley in my link above from our Doc.