Unable to Rebuild or Repair a failing index
EV 9.0.2 running on Server 2008 R2 Standard.
I have come across a small number of indexes which are refusing to rebuild and repair in my current EV environment.
To briefly explain, we had a number of failed indexes identified by using the "Manage Index Volumes" tool. The majority of them rebuilt successfully and the more difficult one were corrected by following this thread: http://www.symantec.com/business/support/index?page=content&id=TECH174186
I am now left with six indexes that produce an event id of 7292:
The index volume has been marked as failed.
index volume: <index volume id followed by username>
index volume path <self explanitory, and is correct>
Reference: Too many consecutive failed items.
Due to errors accessing the index volume it has been marked as 'failed' to prevent further errors. The index volume will remain inaccessible unitl it has been repaired.
Subsequently, the total items that are waiting to be indexed in the vault store has now reached a limit that has raised a critical status alert in the VAC which is slowly increasing as each day passes.
I did read the following thread: https://www-secure.symantec.com/connect/forums/unable-rebuildrepair-failing-index which mentioned making a change to the registry in order to increase the threshold of known errors so that the task of a rebuild\repair does not fail, but as the thread goes, I don't want a quick fix and would rather know what is causing this to happen.
That being said I have run a DTrace on one of the affected achive but I require some assistance with identifying the problem.
This is where I was hoping someone would be able to point me in the right direction.
I have attached the DTrace to this discussion and would appreciate any input should anyone take a look.
Thanks for taking the time to read my post and hopefully someone out there can provide me with some much needed assistance.