Search your drive where the

[Liam_Finn1]

Search your drive where the indexes are stored for indexmissing.log

If you check in the VAC for the archives which were failed yesterday...are they now showing a number of items missing from the indexes in the VAC?

[James_Slack]

Any idea how I can find it.

I have a H: driver called Indexes and I have searched that whole drive and there is no indexmissing.log file.

I also searched the C: drive and it't not hiding there either. Is there a way to confirgure where this file resides (and therefore find out where I need to look).

Cheers

[Liam_Finn1]

it will always be in the directory where the index resides.

If it has not created this file it means that you may not be missing any data from the indexes


Did you restart the services again today (maybe early morning for backups)?

Did you run the last SQL script I gave you to check if there were any missing index items?

 

[James_Slack]

Not sure how to check for this:
"If you check in the VAC for the archives which were failed yesterday...are they now showing a number of items missing from the indexes in the VAC?"

Any info?

[James_Slack]

I will restart the services again manually (maybe use this as an oppertunity to reboot quickly) and then run that script you gave me.

Will report back.

[James_Slack]

I will restart the services again manually (maybe use this as an oppertunity to reboot quickly) and then run that script you gave me.

Will report back. Thanks

[James_Slack]

I will restart the services again manually (maybe use this as an oppertunity to reboot quickly) and then run that script you gave me.

Will report back. Thanks for

[James_Slack]

I will restart the services again manually (maybe use this as an oppertunity to reboot quickly) and then run that script you gave me.

Will report back. Thanks for your

[James_Slack]

I will restart the services again manually (maybe use this as an oppertunity to reboot quickly) and then run that script you gave me.

Will report back. Thanks for your help!!

[Liam_Finn1]

in the VAC expand Archives

Then expand File System or Exchange Mailbox depending which was failed
in the right side window you will see the list of your archives

Select one of the archives which failed and select Properties
When the properties opens select the Index Volumes tab
If you scroll left on that window you will see the Failed Items Column
This will show you if there are any missing items for the users archives
Each line in this represents an index location
If there are any items missing from any of the specific index locations you can highlight the one with the failed items, right click and select repair

EV will then try to add the missing items to the index.

When a repair is running the index will show as rebuilding, in fact it is just adding the missing items and it is not doing a rebuild

[James_Slack]

Had a look at one of the users.

As I said yesterday, the status is NORMAL. If I look at failed items, it shows as NOT SET.

Does this mean all is OK or does it mean that it doesnt know?

[Liam_Finn1]

It looks like all is OK
Sounds like nothing was missing from the indexes.

Whatever was pending to be added was added sucessfully

I would say your indexes are good

[James_Slack]

I used your script and it came back with 1 item, which is an index I am doing a repair on.

So for me, all I needed to do was delete the checksum.dat files and restart indexing. That's pretty handy to know!

Cheers for all your help on this scanner.

[Liam_Finn1]

Anytime, That what we are here for

[Kristjan]

Hi,
I also have a similar problem, after a bad failover in a EV cluster some indexes started to give me errors in the event log:

Event Type:    Error
Event Source:    Enterprise Vault
Event Category:    Index Server
Event ID:    7292
Date:        17.11.2009
Time:        5:29:53
User:        N/A
Computer:   Machinename
Description:
The index volume has been marked as failed.
Index Volume: 15A3407290727264C8A139148C5DF188F1110000Machinename/Volume:72 (archivename)
Index Volume Path: E:\Indexing\Index01\15A3407290727264C8A139148C5DF188F1110000machinename
Reference: Makestable
           
 
Due to errors accessing the index volume it has been marked as 'failed' to prevent further errors.  The index volume will remain inaccessible until it has been repaired.

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
----------------------------------
There are no checksum.dat in those folders and when i tried to update index via admin console, it started to rebuild automaticly

EV version is 2007-SP3

Thanks in advance

[GertjanA]

Hello Kristjan,

I advise to make a new post. this is a closed thread.

Regards

[Liam_Finn1]

 Please create a new post and we will be more than happy to assist you