Forum Discussion

SHI-CRO's avatar
SHI-CRO
Level 6
13 years ago

Indexing metadata folder growing very large

On one of our EV servers, the \EVIndexing\data\indexmetadata\reporting\system-reporting is about 12GB.  On the other servers, they're about 12mb.  Any idea what would cause this type of growth?

Enterprise Vault
Information Governance
  • Tremaine's avatar
    Tremaine
    13 years ago

    A LBN blurb should be on its way shortly. In the interim some additional information here and workaround as needed to control some of the growth if necessary:

    The Reporting logs will normally be capped at 2GB for each daily log and roll over after 7 days = 14GB, however there is a monthly log as well that is unconstrained which is what requires to be fixed in the future release. Creating a readonly file in the folder of the name 'YYYY-MM' will prevent any logging taking place and it growing so the maximum amount of space that should/could be consumed would be 14GB by the daily files only. A new monthly file will need to be created for each month until this issue is addressed.

    Bear in mind this is not a solution as some errors are logged into the monthly file that wouldn't necessarily be in the daily file. This is really just to manage the growth of this location until a fix is available.

3 Replies

Sort By
  • Tremaine's avatar
    Tremaine
    Level 6
    13 years ago

    Typically this could indicate a problem processing a specific Indexvolume or 'Collection'. This is a known defect that is currently being worked and will only be addressed in a future release (post 10.0.1) in order to control the log size.

    If you check your EV Eventlog for indexing errors you may be able to spot which Index is potentially being problematic and it may well require a rebuild in order to address the issue.

    I would suggest you open a case with support and also provide them one of 'dialy' logs that has grown at least so that they can have a look to see what errors are causing them to grow.

    The reporting logs are contained within a SQLLite database so unless you are comfortable/familiar interrogating such DB's it would be better to let the EV support team assist you with this issue.

    If you are still on 10 Base I would highly recommend you upgrade to 10.0.1 as well as that has a number of fixes pertaining to the Indexing engine.

  • AndrewB's avatar
    AndrewB
    Moderator
    13 years ago

    thumbs up to the OP for pointing this out.

    Ghost - in case this is not already in the "Late Breaking News" article please see what you can do to have it added so the community outside of the forums can benefit from this knowledge too.

    Thanks!

  • Tremaine's avatar
    Tremaine
    Level 6
    13 years ago

    A LBN blurb should be on its way shortly. In the interim some additional information here and workaround as needed to control some of the growth if necessary:

    The Reporting logs will normally be capped at 2GB for each daily log and roll over after 7 days = 14GB, however there is a monthly log as well that is unconstrained which is what requires to be fixed in the future release. Creating a readonly file in the folder of the name 'YYYY-MM' will prevent any logging taking place and it growing so the maximum amount of space that should/could be consumed would be 14GB by the daily files only. A new monthly file will need to be created for each month until this issue is addressed.

    Bear in mind this is not a solution as some errors are logged into the monthly file that wouldn't necessarily be in the daily file. This is really just to manage the growth of this location until a fix is available.