Subclient Level Indexing - Index Cache Cleanup

During Indexing Version 2 backup operations, substantial amounts of indexing data and metadata are created. When this data is no longer required, the active index database, index backups, and index logs undergo a series of cleanup and compaction processes.

Index Database Cleanup

To manage space consumption, the index database regularly undergoes cleanup and compaction.

When the index is at the subclient level, the following cleanup is performed:

• Metadata of aged and invalid jobs is removed.

• Metadata of the latest two cycles is retained in the index database. The older cycles are cleaned up regularly.

  The number of cycles to be retained can be changed by using the Advanced Subclient Properties > Indexing > Enable index pruning settings. For more information, see Modifying Index Pruning Settings.

Index Database Backup Cleanup

The system retains and deletes index database backups according to the following rules:

• You can have more than three versions of index database backups for each subclient. Each index database backup has an index of different sets of backup jobs.

• These index database backups are aged as follows:

  • At any time, the system attempts to retain a minimum of the three latest versions of index database backups for each subclient.

  • An index database backup is aged only if all of the backups jobs in it are aged.

  • If an associated backupset is deleted, all of the index database backups of all of the subclients will also be deleted.

Index Log Cleanup

Index logs are cleaned up after the following two conditions are met:

• The index logs are played back into the index database.

• The index database is backed up.