The following error message is displayed when performing a data integrity check:
Index file for destination "%Destination%" of backup set "%Backup Set Name%" is found to be corrupted. It is required to delete all data in this destination to fix this problem. Do you want to do so?
Index corruption may lead to various error messages:
- Failed to commit journal, caused by [RuntimeException] [CommitJournal.run] error
- Missing BDB file while journal file exist
Note: User is prompted to delete all data due to index corruption.
The message suggests that the index files of the corresponding backup set are corrupted.
Our software development team is working on a fix to enhance how index corruption is handled by the client application. In the meantime, to rebuild the index without deleting all existing backed up data, perform the following steps:
On the client computer, delete the local index files:
- Press [No] in the Data Integrity Check utility, then stop the data integrity check.
- Exit from the user interface.
- Delete the local index files within the temp directory of the affected backup set:
- For example:
Note: Delete the entire index folder
On the backup destination, replace the corrupted index files:
- Delete the corrupted index files at:
- Copy the index files from a previous backup job (within the folders with date and time (e.g. YYYY-MM-DD-hh-mm-ss)):
Perform another data integrity check via the user interface afterward.
The steps performed above will revert the backup set's backup data to a previous backup job, therefore, data backed up by the latest backup job will not be restorable.
It is also strongly recommended that all backup sets are configured to backup to multiple backup destinations, to provide user with data redundancy and backup / restore flexibility.