Issues during the indexing process can result in items not being added to a given archive's index.  Individual items are added into one specific index volume of an archive's index and failures with that item are logged in the IndexMissing.log file in that index volume folder.  More information about the IndexMissing.log file can be found in technical article: "How to read the contents of the IndexMissing.log file" in the Related Documents section at the end of this article.

Note that volumes will only be marked as failed due to missing items when the number of missing items is above a specific threshold - 25 by default.  See the Technical Note: "Tuning your Enterprise Vault Indexing environment" for more information about the registry key that affects this setting.

Evidence of failure to add items to an index can be seen in multiple places.  See the pictures below for what this looks like.

From Enterprise Vault Administration Console:

 

From the index volume folder:

 

From the Discovery Accelerator or Compliance Accelerator client (8.0 or later):

 

Resolution:

Method 1:

The first, and easiest method of resolving this is to simply repair the given index volume:

 

This will work if there was simply a disruption in processing the item initially and there are no other problems with the item(s).

Method 2:

One possibility to consider is that the information in the IndexMissing.log file is incorrect.  To check this, see the technical article "How to read the contents of the IndexMissing.log" in the Related Documents section at the bottom of this article and open the IndexMissing.log file in question and confirm that the contents appear to be formatted correctly.

For instance, if there are two (or more) header lines in an IndexMissing.log file, this is a sign of IndexMissing.log corruption.  Example:

187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias/Volume:3
187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias/Volume:3
695010,201004020246464~201001212344150000~Z~E129CCEDDEA7D66713C63676F395D731,-1

How to locate the IndexMissing.log file:

Note: It is assumed in this section that the archive in question has already been located and the specific index volume is already known.  For information about how to locate these when these are not known, see technical article: "Maintaining your Enterprise Vault Indexing environment" in the Related Documents section at the end of this article.
 

1) Within the Enterprise Vault Admin Console (VAC), on the "Index Volumes" tab of the properties of the affected archive, hilight the affected index volume.

2) Expand the third column "Location".  This gives the relative location to the folder that contains the files associated with this index volume - on the Indexing server that hosts this index volume.

3) Click on the Advanced tab and select, from left to right, the "Archive ID" at the bottom of the display (this is frequently a long value and the entire value is not always displayed).  Copy this value into notepad or another convenient location.

4) Assuming that this index volume is located on "serverA", browse to: "C:\EVStorage\index\index1\"

5) At that location are many files.  At the bottom of this listing of files should be the "IndexMissing.log" file.

If the IndexMissing.log file is corrupt, it will need to be rebuilt.  If it appears to be correct, but "Method 1" does not work, rebuild the IndexMissing.log file.

Procedure to rebuild the IndexMissing.log file:
 

1) Stop the Enterprise Vault Indexing service,

2) Backup the affected index volume folder,

3) Rename the "IndexMissing.log" file (e.g. "IndexMissing.old")

4) Run the following indexcheck command:

indexcheck -c missingdocs -f -db

5) Verify that the IndexMissing.log file has a correct format (see technical article: "How to read the contents of the IndexMissing.log file").

a) If this file does not rebuild correctly, contact Veritas Support Services

b) If the file does not reappear - it could be that no items are actually missing.

c) If the file reappears and is formatted correctly, check the contents of the old file and the new file.  If they are different, return to "Method 1".  If they are the same, continue on.

6) Start the Enterprise Vault Indexing service.

Sample output of an IndexMissing.log rebuild:

C:\Program Files (x86)\Enterprise Vault>indexcheck -c missingdocs -f "C:\EVStorage\index\index1\187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias" -db
sql
Start time: 5/31/2010 12:46:43 PM

****************************************************************************
***                             WARNING!                                 ***
***                                                                      ***
***  Running this tool on an index which is being used by a live system  ***
***  may cause the index  volume to become unstable or corrupt.          ***
***                                                                      ***
***  It is strongly advised that this tool is only run on COPIES of      ***
***  index folders which are not referenced by a live system, or on a    ***
***  system where the indexing service is not running.                   ***
***                                                                      ***
****************************************************************************

Are you sure you wish to proceed? (yes/no) yes

****************************************************************************
***                             WARNING!                                 ***
***  Running 'MissingDocs' or 'MissingContent' checks will cause the     ***
***  log file(s) to be overwritten.                                      ***
***                                                                      ***
***  Please make sure the file(s) are backed up before continuing with   ***
***  this option.                                                        ***
***  It is also highly recommended that the Indexing Service is shutdown ***
***  before starting.                                                    ***
***                                                                      ***
****************************************************************************

Are you sure you wish to proceed? (yes/no) yes
 Processing index folder C:\EVStorage\index\index1\187938EFF4AB230468C40C1130E4E0F1E1110000ev8alias
 Scanning ISN range [1 - 215] for missing items...
 WARNING!  Failed items have been added to the "IndexMissing.log" file.
 Finished. Checked 1 index(es), 0 with errors, 1 with warnings
End time: 5/31/2010 12:46:47 PM
Duration: 0 minute(s) 4 second(s)

C:\Program Files (x86)\Enterprise Vault>

Method 3

If the previous two methods do not work, it is possible that the items are missing from Enterprise Vault storage.  Verify that the items in question are actually present in their associated Enterprise Vault store partition. This can be done using the procedure outlined in Related Article HOWTO37697. 

 

If the file(s) is confirmed missing or fails the retrieval process from the step above, when possible, restore it from backup.  In the case where the vault stores are on an EMC Centera, it would be required to contact EMC support to verify validity of the SaveSets in question.  

If you are able to restore the files successfully, start again with Method 1.