Automatic recovery from error on index corruption or index playback error
Beginning in Commvault Platform Release 2023 (11.30), user intervention is not needed when an index becomes corrupted or if there is an index playback error. This applies to File System Agents using subclient level index, as well as Virtual Server Agents.
If a MediaAgent shuts down unexpectedly during the index playback, or if the disk where the index cache is located becomes corrupted, the index for one or more clients can become corrupted. If this occurs, the system recovers the index automatically as follows:
-
The system marks the corrupted index "critical" in the Index State Report.
-
When a subsequent operation attempts to access the corrupted index (for example, browse or restore), the system automatically triggers a reconstruction of the index and the index is reconstructed using the latest cycle for the subclient.
-
If a full backup job is run, the system automatically creates a new index without requiring any index restores of previous cycles. Once the index is found to be corrupt in the index cache, if a full job is run, the corrupt index is cleared and a new index is created by playing back the full job. Since automatic reconstruction of the index is only for the latest cycle, this method avoids index restores of previous cycles. This is helpful when media for a previous cycle is corrupted or unaccessible.
-
The system will back up the index only after it is completely recovered and is no longer corrupted. Therefore, you do not need to invalidate bad index backups.
Backup is pending with error code [14.96] [14.95] "Failed to start createIndex on MediaAgent..."
For more information, see KB Article IND0009.
Backup is pending with error code [32:406]
This error code can have either of these basic descriptions:
-
The index cache for the MediaAgent is disabled.
-
The MediaAgent is not active.
For more information, see KB Article IND0004.
Backup is pending with error code [82:156] "The destination encountered an error while processing the data from the source"
For more information, see KB Article IND0005.
Cannot Upgrade to Indexing V2 Because of Missing Index
For more information, see KB Article IND0006.
Error Code [14:72] "Out of cache space after trying to free...blocks in cache area..."
For more information, see KB Article IND0010.
Index has not been backed up for past 30 days
There are two possible reasons that an index has not been backed up for the past 30 days:
-
The MediaAgent and/or disk library where the index is expected to be backed up have been offline for more than 30 days, therefore no backups have been run during this time. To correct this issue, ensure that the MediaAgent and/or disk library are online.
-
The index is not up to date, and one or more of its playback operations are failing. In most cases, this is caused by hardware performance issues. To correct these issues, ensure that the index cache disk meets Hardware Requirements.
Index Server MediaAgent is Taken Offline because Index Cache is Full
For more information, see KB article IND0012.