Index restore jobs initiated and failed

The Big Data Apps clients protect each VM’s Indexing Database and the VM backups transaction log files to secondary media. These Big Data Apps clients are automatically created per Storage Policy that is leveraged for VM backups.

With your transition from Tape to HSX, the operations you’re actioning require an Index that may require a reconstruction of the Index Databases involved across your VMs. The Index Restore operation should state which tapes are required to rebuild the Indexing Databases. You may have to open a Customer Support case to review the log files and reports to further help you out here. However, most of the time, its a matter of collecting and placing the tapes into the library to complete the reconstructions.

When you say, moving from tape to HSX. Are you auxcopying the data from the tape copy to the HSX copy, or have you simply created a new plan or storage policy and pointed your VMs to backup there now?

With indexing V2, the indexes are persistent and are maintained on particular media agents.

Do the old media agents still exist?

You might have to change the indexing media agent: https://documentation.commvault.com/2024e/expert/changing_indexing_mediaagent_indexing_version_2.html

Dear Damian,

I mean that we created a new SP and pointed the VM backup to it, Tape library and HSX are on different media agents

Note that the index restore jobs are for the index server of the old SP not the new one.

Thanks

Dear Wgrande,

Thanks for your support.