Problem with Optimized Scan - failed files and folders

Question

Hi All,

During backup with the file system agent, even though the jobs are in the completed status, Commvault reports many Failed Folders and Failed Files.

The Optimized scan option is currently selected.

Interestingly, the logs show that Commvault is trying to access locations that no longer exist physically.

After changing to Journal, there were no such problems (there were no failed folders and failed files).

After returning to Optimized scan, the problem appeared again.

This is version 11.32 with new fixes.

Looking for information about the scanning option in the documentation, I understood that Change Journal is used for the NTFS file system and most often when the Optimized scan option is unavailable, or the metadata database created by Optimized scan is corrupted.

File Scan Methods for the Windows File System Agent

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

Subclient Properties (Advanced Options)

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

So, will deleting the metadata database on the client cause it to be rebuilt and may eliminate the problem, or will deleting it cause problems and is better not to do it?

The procedure I found:

What is the procedure to delete the Optimized Scan database on Windows?

https://documentation.commvault.com/v11/expert/frequently_asked_questions_03.html#what-is-the-procedure-to-delete-the-optimized-scan-database-on-windows

Or how to repair this database if restarting services alone does not help?

Of course, my suspicions fell on the metadata database, but I could be wrong.

Please help if someone has had similar experiences in this topic.

Thanks to everyone in advance for your help.

Best answer by Jace Ross

Hi Kago,

Optimized scan functions similarly to change journaling just leveraging a DB for change tracking.
Typically I’d suggest the content selected is causing the issue but given switching to Change Journal scan resolved the issue, I would suggest there’s an issue with the optimized scan DB.

The link you shared deletes the DB and this is the recommended procedure for a situation like yours.

I would suggest you follow the steps in the document and try a full, then incremental backup with optimized scan enabled and see if the issue persists.

Jace Ross · Accepted Answer

Hi Kago,Optimized scan functions similarly to change journaling just leveraging a DB for change tracking.Typically I’d suggest the content selected is causing the issue but given switching to Change Journal scan resolved the issue, I would suggest there’s an issue with the optimized scan DB.The link you shared deletes the DB and this is the recommended procedure for a situation like yours.I would suggest you follow the steps in the document and try a full, then incremental backup with optimized scan enabled and see if the issue persists.

kago · Answer

Hi Jace,Thanks for the advice. I'll try to remove the optimized scan DB and run a backup (full) with optimized scan then, next incremental and let you know if that helped.Regards

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded