Hi @Glen 

Thank you for the question and welcome to the Community!

This certainly sounds like the optimized file scan database on the client has an issue and the next step is to rebuild.

Please check for the presence of registry key:
Location : HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\Data Classification\Configuration\{GUID}\ 
Key Name : DatabaseRebuildControl
Type : DWORD 
Value : 3

This marker governs if the database should be rebuilt on the next services restart.

Please restart all client services and you should the database get rebuilt. The database can be found in this location, but as you suggest, there will be a separate database per volume:

C:\System Volume Information\Commvault\Data Classification

The database will named something similar to “dc_002.db”.

There are also steps mentioned in documentation for manually deleting the database if this automatic process doesn’t yield results:

Windows Backup Agent - FAQ

Thanks,

Stuart

Thanks Stuart,

Sorted after the restart of the services (key was present).

Cheers,
Glen.

Thanks for confirmation @Glen!

Glad that got it sorted.

Thanks,

Stuart

Hi @Stuart Painter 

short question, is there also an additional setting wich we could use?

Thanks

Martin

Hi @martinkaufmann 

No, unfortunately there isn’t an additional setting for this.

Since the key needs to configured using the database GUID itself, we wouldn’t be able to add the key DatabaseRebuildControl as an additional setting since the registry location requires the GUID in the registry folder path.

In theory this is a niche use-case, with this manual intervention needed only if a database has an issue.

Thanks,

Stuart