Video Screencast Help

How to create Index data not in Index backup

Created: 21 Jan 2014 • Updated: 19 Feb 2014 | 4 comments's picture
This issue has been solved. See solution.

Dear  Team,

We  have taken backup of Index data through  EV agent by NBU. Now EV not in backup mode. We are  restoring  index data  and it will be  available for  EV.

This backup is 7 days old  and  EV has created new index data  also. I want to use restore data and delete  data which is currently in use by EV. Please

help me  how can i use missing index  data.


Prajyot K

Operating Systems:

Comments 4 CommentsJump to latest comment

Arjun Shelke's picture

Hi Prajyot,

Are you doing this restore as a part of troubleshooting any issue? I assume you have failed Indexes, which you are trying to rebuild using the old index data from backups.

GabeV's picture

Hi Parjyot,

If the indexes have one week of missing data, you can update the index volumes, as long as you have the data in the storage and the databases are up-to-date. What version of Enterprise Vault do you have? If you are running EV 10, you can create a subtask and update several index volumes simultaneously and add the rest of the index volumes to the subtask queue doing right click over the Indexing > Manage Indexes in the VAC. For Enterprise Vault 9.x, you can update the index volumes in batches. I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

GabeV's picture

Take a look at these technotes:

Enterprise Vault - Restoring an index from backup

Enterprise Vault 10 Feature Briefings - Indexing Update

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

JesusWept3's picture

You don't even really need to do a synchronize or an update on the indexes.
Any failed indexes will be marked to online every 2 hours, any time a search is made, or item archived etc, or anything that looks at the index, that will cause the index to do an internal check, notise that its internal index entry is lower than the highest ISN in the database and perform an update from there.

So even if you were trying to be really careful about not overloading the system by doing it in batches, if users run a search, or you use a search in DA or you do a vault cache build, it will all trigger index updates anyway