State.dat file is not getting updated on the journal Archive index causing indexing to halt

[SameerV]

Hi 

We are facing issue with the journal Archive index ,the item awaiting count for indeexing is growing .when i check the index volume that has data written on it the state.dat file does not get updated causing the indexing to halt 

Reboot resolves the issue

[GertjanA]

HEllo Sameer.

Which version. Please add basic information in your questions.

Such as: EV version, kind of archiving, archiving target version, sql version. Sometimes there is an issue with a specific version, which is resolved in a SP, CHF or newer version.

Thanks!

[SameerV]

EV is Ev11 Sp1 with CHF1

Journal/Mailbox Archiving
Archiving target version:exchange 2013 CU9

All the archives indexes are working fine

Only Journal Archive indexing is not getting updated 

I have open the state.dat file it shows the below

<?xml version="1.0"?>

<IndexVolumeInternalState Id="1C115FA9DE3F95C4C9B0606F9B204F10A1110000colliersvault.anz.corp.local_13360">

  <Actions>

    <Additions AcknowledgedCount="330644" HighestSubmittedSequenceNumber="28070986" HighestAcknowledgedSequenceNumber="28070986" LastAcknowledged="2016-06-01T16:40:56.7440154Z" />

    <Deletions AcknowledgedCount="0" HighestSubmittedSequenceNumber="0" HighestAcknowledgedSequenceNumber="0" LastAcknowledged="0001-01-01T00:00:00" />

    <Updates AcknowledgedCount="0" HighestSubmittedSequenceNumber="0" HighestAcknowledgedSequenceNumber="0" LastAcknowledged="0001-01-01T00:00:00" />

  </Actions>

</IndexVolumeInternalState>

so I believe it does not have the update information since it was not accessed 

[GertjanA]

You need to upgrade to CHF5. (you can do CHF4, has fix for this, but CHF5 is latest available CHF for 11.0.1) => http://www.veritas.com/docs/000106004

There was an issue pre CHF4, described as below:

Items on the storage queue could cause an indexing backlog to occur [3775557]
 
When an error occurred that prevented items on the storage queue from being archived, it caused an indexing backlog.

This has been fixed. Once an item has been on the storage queue for more than 15 minutes, indexing continues.

Notes:
•A maximum of three attempts are made to index an item still on the storage queue.
•If the vault store is in backup mode, or there are no open partitions,
the 15-minute time limit is not enforced and any item still on the storage queue prevents indexing of further items.

This issue occurrs when there was a problem with the storagequeue. For instance, when performing an DR.

[GertjanA]

Hello Sameer,

If you are happy with an answer, can you please mark that as solution?

Thanks.