01-21-2014 01:59 AM
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.
Regards
Prajyot K
Solved! Go to Solution.
01-21-2014 10:31 AM
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
01-21-2014 03:53 AM
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.
01-21-2014 05:56 AM
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.
01-21-2014 06:07 AM
Take a look at these technotes:
Enterprise Vault - Restoring an index from backup
http://www.symantec.com/docs/TECH188086
Enterprise Vault 10 Feature Briefings - Indexing Update
http://www.symantec.com/docs/DOC5632
01-21-2014 10:31 AM
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