Forum Discussion

The-EV-Guy's avatar
The-EV-Guy
Level 2
10 years ago

Index volume update percentage complete in excess of 100%

One of the index volumes in our EV 8.0 SP5 environment is currently being updated, but the information being written to the event logs doesn't make any sense, the following is an example of one of the events.

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          17/03/2015 11:21:03
Event ID:      7314
Task Category: Index Server
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      servername.domain.company.com
Description:
Index volume update in progress 

Index Volume: 129E90C9A16A6B34994D278130C2DE4371110000EV-Archive/Volume:***** (SERVERNAME) 

Percentage completed: 150% 
Estimated time of completion: 17/03/2015 09:27 

Index Volume Path: I:\Indexes\index1\129E90C9A16A6B34994D278130C2DE4371110000EV-Archive_106493413 
Job Id: Vol_68957 
Job Author: Indexing Service 
Job Description: Update rollover index volume 

Job elapsed time: 16:55:53 (hours:minutes:seconds) 
Processing time: 16:54:48 (hours:minutes:seconds) 
Number of items added: 721608 
Number of items additions abandoned: 0 
Number of items deleted: 0 
Number of items updated: 0 

How can an index be 150% updated and how can the estimated time of completion be in the past?

Is there any way to accurately determine when the update will actually finish?

 

Enterprise Vault
Information Governance
Tip-How to
Troubleshooting
Windows Server (2003-2008)
  • JesusWept3's avatar
    JesusWept3
    10 years ago

    Typically its because you start the index rebuild, it see's it has 100 items to index
    as its indexing, more items and more items get added
    so if 50 items get added after the index rebuild process starts but before its finished, you have index 150 items, and that is 150% complete etc

    it's silly logic but can be normal, especially for journals or users doing PST Imports etc

  • TonySterling's avatar
    TonySterling
    Moderator
    10 years ago

    This has been seen in the past and from the looks of things the user choose to rebuild the entire index.

    https://www-secure.symantec.com/connect/forums/index-server-percentage-completed-295

    You could either let it finish or do a rebuild of it.  It looks like it has been running for 16 hours though, so it may take a good bit.

     

     

  • JesusWept3's avatar
    JesusWept3
    Level 6
    10 years ago

    Typically its because you start the index rebuild, it see's it has 100 items to index
    as its indexing, more items and more items get added
    so if 50 items get added after the index rebuild process starts but before its finished, you have index 150 items, and that is 150% complete etc

    it's silly logic but can be normal, especially for journals or users doing PST Imports etc

  • The-EV-Guy's avatar
    The-EV-Guy
    Level 2
    10 years ago

    Thanks for your response, I suspect this might have been the case and it was a journal archive that was being investigated.

     

    Thanks for clearing that up.