Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

EV 10 Index Upgrade - Success, Warnings, Failed - When to retry or rebuild?

Created: 08 Oct 2012 • Updated: 08 Oct 2012 | 5 comments
DeadEyedJacks's picture
This issue has been solved. See solution.

OK,

Following an EV9 to EV10 upgrade I have around 3000 indexes to upgrade.

I setup batches of tasks grouped by vault store / mail store.

 

Some show as "Successful, Missing Content" others as "Successful Items with Errors"

There's no retry option in these cases, so should I  be concerned and what course of action is there?

Is a rebuild or verify of the new 64bit index appropriate or worthwhile? 

 

Where subtasks failed due to overloaded storage / index resources there is a retry option.

So that seems clear cut.

 

Thanks in advance

 

Comments 5 CommentsJump to latest comment

JesusWept3's picture

a retry would just simply be Synchronize

DeadEyedJacks's picture

JW,

OK, I've realised "Missing Content" means the same as the EV Convertor events. 

Items that couldn't be converted due to being too large, unknown format, encrypted, etc.

So can be considered a succesful index upgrade.

 

But what about "Successful with Warnings, Items with Errors"?

08/10/2012 11:55:55 Upgrade summary:
08/10/2012 11:55:55     Total items indexed: 1359988, 1592 item(s) with missing content
08/10/2012 11:55:55     Total failed items: 124
08/10/2012 11:55:55     Total items processed: 1360112
08/10/2012 11:55:55 The upgrade has completed successfully and reported some issues.
 

05/10/2012 11:44:40 The following items failed to be indexed into the new index volume:
SeqNo    SSID    URL    Error Code    Raw Error
303632    Unavailable    Unavailable    106    
303661    Unavailable    Unavailable    106    
...

It's a large journal archive with 30+ index volumes, so is it worthwhile doing a synchronise?

 

On a related topic,

With multiple tasks and subtasks queued up for the index service, how does the system decide which subtask to process next?

When / How does it determine that the indexing service is overloaded and stop activating further subtasks?

 

TIA

D

 

 

 

Authorised Symantec Consultant on Archiving and eDiscovery ASC, STS, SCS, SSE+

Microsoft, NetApp and VMware certified professional MCTS, MCSE, MCSA, NCDA, NCIE-BR, VCP, VTSP

DeadEyedJacks's picture

And to answer my on question in part.

The Enterprise Vault Server Properties now contain on Advanced tab with the Indexing server thresholds and parameters.

Authorised Symantec Consultant on Archiving and eDiscovery ASC, STS, SCS, SSE+

Microsoft, NetApp and VMware certified professional MCTS, MCSE, MCSA, NCDA, NCIE-BR, VCP, VTSP

TonySterling's picture

I doubt it would be worth it to Synchronize as you have discovered the reason some of the items weren't able to be indexed.

DeadEyedJacks's picture

It's OK, I've found these to articles which explain what the Failed Items Error Codes mean.

http://www.symantec.com/business/support/index?pag...

http://www.symantec.com/business/support/index?pag...

Authorised Symantec Consultant on Archiving and eDiscovery ASC, STS, SCS, SSE+

Microsoft, NetApp and VMware certified professional MCTS, MCSE, MCSA, NCDA, NCIE-BR, VCP, VTSP

SOLUTION