Forum Discussion

AKL's avatar
AKL
Level 6
13 years ago

Journal Index Stuck at "Rebuilding"

Hello All

I've been assgined as an administrator to a running EV environment. The administrator prior to me, for some reason started rebuild of an historic journal archive with millions of items - majority of which are on legal hold & marked for deletion as well based on expiry.

It wasn't a concern, however still to fix same, I used HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Indexing <DWORD> MaxConsecutivePoisonPillItems = 0 as discussed in below forum:

Also tried to go through below article for any help that i can get to complete the rebuilding of index, but no break through yet:

Now I need to document upgrade from 9.0.1 to 10.0.2 and the rebuilding index might cause a road block. Any ideas if there's a way to get the index rebuilding to finsih line in few months time? And if not, is it ok to upgrade while the index is rebuilding (to my understanding it should close this index and open a new x64 one)

Thanks in advance !

Enterprise Vault
Information Governance
Troubleshooting
  • Jeff_Shotton's avatar
    Jeff_Shotton
    13 years ago

    Are you going to rebuild the index to x64 bit after you move to 10.0.2? After all, it is optional wether you choose to do this for historic items. If the answer is yes, then you may as well upgrade as soon as possible to avoid duplicating the workload. Given hardware which is EV10 capable, the index will rebuild faster on EV10 than EV9. Yes it will use more resource...but then it CAN use more resource.

    I'm sure i remember reading somewhere that it isnt advisable to upgrade while the index is rebuilding, but since it is rebuilding from storage rather than translating the old index, it seems a little pointless to wait. You are correct that it will create a new x64 index on the upgrade. Essentially 32bit indexes become read-only

    EV10 indexing design and best practice: http://www.symantec.com/docs/DOC4250

    Regards,

    Jeff

  • Jeff_Shotton's avatar
    Jeff_Shotton
    Level 6
    13 years ago

    Are you going to rebuild the index to x64 bit after you move to 10.0.2? After all, it is optional wether you choose to do this for historic items. If the answer is yes, then you may as well upgrade as soon as possible to avoid duplicating the workload. Given hardware which is EV10 capable, the index will rebuild faster on EV10 than EV9. Yes it will use more resource...but then it CAN use more resource.

    I'm sure i remember reading somewhere that it isnt advisable to upgrade while the index is rebuilding, but since it is rebuilding from storage rather than translating the old index, it seems a little pointless to wait. You are correct that it will create a new x64 index on the upgrade. Essentially 32bit indexes become read-only

    EV10 indexing design and best practice: http://www.symantec.com/docs/DOC4250

    Regards,

    Jeff

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    Thanks Jesus & Jeff

    I am trying to track down the progress as instructed in article atm.

    And I believe we should be ok even if index gets closed, since it shouldn't exist in first place due to expiry, but will the item deletions be impacted if indexes is closed? (I am 80% sure answer is yes, but still double checking)

  • Jeff_Shotton's avatar
    Jeff_Shotton
    Level 6
    13 years ago

    AKL,

    No they won't be impacted. You will still be able to delete data from an index residing in a closed partition. You are closing the partition to accepting new indexes in EV9 and new data in EV10, but deletes are still possible.

    Regards,

    Jeff

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    Hello Jesus

    I apologize for delayed response, but I finally got chance to sit 10 minutes and try to trace down the rebuilding progress.

    As per article, I couldn't find Event ID 7305. I ran the SQL query and checked the updates.log from said folder and determined that there's no entry to it since 2011, below was the 1 line entry for same:

    2011-02-09 17:02:24.247 M Index commit (Makestable) Reason=Search Request Item Seq Num=49447863 Delete Seq Num=0 Items added=0 Words added=0 Items deleted=0 Elapsed(secs)=1.0
     

    Would it be safe to flip the rebuilding flag in SQL database/Index volume table? OR should I initiate another rebuild? OR let the EV ugprade and close the partition since it won't be used?

  • JesusWept3's avatar
    JesusWept3
    Level 6
    13 years ago

    To be honest I think Jeff is spot on, upgrade to EV10 then do the rebuild, cos you're going to have to do it any way, if you're going to spend all that time rebuilding it, might as well be for the latest and greatest and such

  • AKL's avatar
    AKL
    Level 6
    13 years ago

    Thanks again Jeff & Jesus. Will let you know how upgrade goes soon !