cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot repair or delete failed indexes

I have a client that has rebuilt and repaired indexes.  He has millions of e-mail, but a few, maybe a total of 28 e-mails, will not repair.  We have restarted the services, tried numeorou repairs, but still they do not say "successful". This is a DTrace of the issue:

Enterprise Vault 2007.x

1. Within the Vault Admin Console, expand Archives and go to the Properties of the archive in question.

2. Click on the Index Volumes tab, right-click the index volume and select Repair Index Volume.

This will retry indexing of failed items.

The process starts, but we receive the following error:





Have, checked and the DVS files do exist, so it looks like the Storage service is having problems reading these items. Also looking back through historic Discovery Accelerator searches doesn't show any issue, so looks they were included in the indexes previously.

The indexes have been rebuilt several times over the last few years, so suspect that a subsequent rebuild has had this issue.

A quick Dtrace of on Indexing produced the following errors:

706947 11:09:14.319 [1144] (StorageCrawler) <3760> EV:L CItemFetcher::WaitForItem Request Info: [6600468, IndexMetadata, 10240 (KB), 4337892, 117E8CE40D985BB448C7D4876AF38CBB01110000kvs+151000000000000~200507041750450000~0~0B28B594438348C5880B8187C4C9FEF+0++0+1+39302.66540312500000000+33273+6600468++4+1+6600468, 6600468, The data necessary to complete this operation is not yet available. [0x8000000a]]

871332 11:09:21.975 [1144] (StorageCrawler) <7060> EV:M CArchiveRevisions::GetIndexMetadata ArchiveID:1CBCAECCA07C6374A85E33971484550681110000kvs (JournHist08) SavesetDescriptor:117E8CE40D985BB448C7D4876AF38CBB01110000kvs+151000000000000~200507041750450000~0~0B28B594438348C5880B8187C4C9FEF+0++0+1+39302.66540312500000000+33273+6600468++4+1+6600468 RebuildMode:1 (hr=Abnormal error occurred Error: %1 Reference: %2 Info: %3 %4 %5 [0xc0041a47])

871346 11:09:21.975 [1144] (StorageCrawler) <7060> EV:L CItemFetcher::FindFirstPendingRequest [0] Request Info: [6600468, IndexMetadata, 10240 (KB), 4337892, 117E8CE40D985BB448C7D4876AF38CBB01110000kvs+151000000000000~200507041750450000~0~0B28B594438348C5880B8187C4C9FEF+0++0+1+39302.66540312500000000+33273+6600468++4+1+6600468, 6600468, The operation could not be completed. A retry should be performed. [0x800704d5]]
 

 

1 Solution

Accepted Solutions
Accepted Solution!

Has this been resolved?

Has this been resolved?

cloudficient - EV Migration, creators of EVComplete.

View solution in original post

12 Replies

Hi GinniCool, So if you this

Hi GinniCool,

So if you this far please look at the indexablie item within the saveset.  DVSSpy is your friend, the saveset could be there but could also be corrupt saveset that is throwing you. 

--wayne

How do I get or get to

How do I get or get to DVSSpy?

Hmmm that's the hard

Hmmm that's the hard question. DVSSpy according to support is not allowed to be given out. It is normally copied via web-ex when needed and then deleted by support before the disconnect from your server.

It is proprietary and not freely available

GianniCool, can you open a

GianniCool, can you open a case with Symantec?

Giann, If the message in

Giann,

If the message in question is not sensitive you could send it to me and I can take a look at it for you...

--wayne

I'm a TSPP Partner, Sigma

I'm a TSPP Partner, Sigma Solutions, Inc.  How come I can't get this software?

As Nicola said, I forgot this

As Nicola said, I forgot this tool is not public :(  you will need to open a support case, and get them to look at the saveset.

OK Wayne...Where do I send

OK Wayne...Where do I send it?

Just sent you a PM

Just sent you a PM
Accepted Solution!

Has this been resolved?

Has this been resolved?

cloudficient - EV Migration, creators of EVComplete.

View solution in original post

Anyone? :) Hello? :)

Anyone? :) Hello? :)

cloudficient - EV Migration, creators of EVComplete.

I have not heard if this has

I have not heard if this has been fixed or not either so i think it is safe to assume this is a dead thread