Index cache getting full in short time

Hello,

The pruning process will differ for V1 and V2 indexing,

A) Regarding V1 indexing:

*******************************

1) 'Index Retention Time in Days' and 'Index Cleanup Percent'.

2) Index files are kept in the index directory for a default of 15 days or until the directory disk reaches 90% disk capacity.

3) Index files are pruned from the index based on least recently accessed.

4) This means that older index files that have been more recently accessed may be kept in the directory while newer index files that have not been accessed are deleted.

B) Regarding V2 indexing:

*******************************

During the index backup we have the below phases,

1) A database checkpoint

2) The database is compacted

3) The database will be backedup.

Database Checkpoint:

***************************

Checkpoints are used to indicate a point-in-time in which a database was backed up. Once the database is protected to storage, any logs that are older than the checkpoint can be deleted from the index directory location.

Database Compaction:

***************************

During data aging operations, deleted jobs are marked in the database as unrecoverable, but objects associated with the job remain in the database. The compaction operation deletes all aged objects and compacts the database.

Database Backup:

*********************

Once the checkpoint and compaction occur, the database is backed up to the primary copy location of the storage policy.

So, if it is a V2 indexing please check the status of the index backup.

Also, I would like to share the below documents,

 https://documentation.commvault.com/2024e/expert/system_and_hardware_requirements_indexing_version_1.html

https://documentation.commvault.com/2024e/expert/system_and_hardware_requirements_indexing_version_2.html

Note:

*******

V2 indexing provides improved performance and resiliency while shrinking the size of index files in the index directory and in storage.

V2 indexing works by using a persistent index database maintained at the backup set level. During subclient data protection jobs, log files are generated with all protected objects and placed into the index database.

Now we have a feature of subclient level indexing

Please refer to the below documents,

https://documentation.commvault.com/v11/expert/indexing_version_2.html

https://documentation.commvault.com/v11/expert/agents_that_use_indexing_indexing_version_1_and_indexing_version_2.html

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

Regards,

Wasim

Hi ​@Index disk space increasing ,

Once you have reviewed the above Technote, you can also use a Tool (TreeSize) to check the largest folders.

Otherwise, can you log a case with Support so we can review.

Best Regards,

Sebastien

Hi Sebastien,

Good day,

.

We have already tried installing that but in our environment due to some security issues we are unable to install treesize tool.

​@Index disk space increasing ,

You can check the size of the below folders (C:\Program Files\Commvault\ContentStore\IndexCache):

yeah, I have verified only CV_Index folder is near to 450GB.

What may be the issue 

That’s V1 Indexing, are there old or new folders?

Maybe Cleanup is not working or Retention is too high.

What is the Index Retention?

No, its V2 indexing and we see new folders 

No, we are using v2indexing and we see new folders.

Retain index for: 10days

Generate alerts when free space falls below: 10GB

Take the index offline when free space falls below: 7GB

Cleanup until free space is at least: 10Percent.

ok, then I think the best is to log a case with Support so we can review as it looks like you have a few Agents running V1 Indexing maybe.