Failed Index Volume
We have EV 10.0.3 for Exchange 2007 and recently we ended up with Indexing issue on only Journal mailbox. We cannot search on Journal mailbox from December 2012. Going to Indexing on the EV console we can see 1 failed index. Indexing and searching is fine for all other users.
We recently migrated from EV 8 to 10.0.1 and this is where after a while one of he Journal indexing volume (64-bit) failed and this is the only 64 bit indexing for Journal archive.
We have tried various fixes including:
verifying and Synchronise.
Some of the event logs suggested to upgrade to EV 10.0.3 and we done the upgrade but not luck with the fix.
Symantec support suggested to use EVSVR to locate the missing items. then we applied EVSVR in report mode and then in repair mode it identified the missing items and deleted them from the indexing.
then it was suggested to rebuild the indexes (only for the failed volume) and we done that and completed the rebuilding. the failed index on the Indexing went a way for a short time then restarting the index server it brought back the failed status and showing error id 28998 and 41329 (Error Type: FrenzyErrorDetected).
I am not sure what else we need to do as I believe Symantec is running out of options here.
Any suggestions or ideas please.
There were two subfolders
There were two subfolders that appear to be missing in the Storage area for Enterprise Vault.
EV pointing to missing DVS files in these locations that were attempting to be indexed. The Index Service was hanging on searching for these items causing the JournalArchive table to build up with items ready to be committed to index.
Since there were not any backups to restore the DVS Files back to this folder, the pointers in the Vault Store database were removed using the DeleteSingleSaveset procedure. Once these pointers were removed, the Journal Index Volume started to update correctly and cleared the items waiting to be indexed from the JournalArchive table of the Vault Store.
it's not known how and why these items gone missing completley despite of having backing up EV every night.
It took over three months to completly fix this issue. I hope this will not happen to anyone elae during the EV migration to 10.0.