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

Enterprise Vault Index File size

Created: 26 Sep 2012 • Updated: 08 Oct 2012 | 3 comments
This issue has been solved. See solution.

How large should the index files become before they are closed and an new one is created. Ours are at 9 Gb per index file but I was wondering what the practice was in the real world. Thanks.

Comments 3 CommentsJump to latest comment

TonySterling's picture

The Index Volumes for individual archives will rollover automatically, you don't have to manually do anything.  The Index locations can be closed as needed to accommodate your backup solution, is that what you mean?

Also, here is the BP doc for your consideration.

Enterprise Vault 10.0 - Indexing Design and Implementation Best Practices

Article:DOC4250  |  Created: 2011-06-08  |  Updated: 2012-04-19  |  Article URL http://www.symantec.com/docs/DOC4250

 

SOLUTION
Jeff Shotton's picture

For a journal generally they reach something like 15-20GB in EV9 before rolling over if using full indexing and default settings. In EV9 (32bit indexes) rollover was based on the number of indexing 'locations' which were utilized. The default maximum was 1 billion, which generally equated to approximately 1 million items  - but it depended on the average size of the items you were archiving.

http://www.symantec.com/docs/TECH53162

With EV10 for journal archiving the indexes are set to roll over after indexing 5 million documents (so a different measure), which means large documents will create much larger indexes...but not with 14x as many items like the best practices document suggests - its closer to 4-8 times in the real world. I've yet to see any statistically significant numbers of journal indexes in EV10, but as a rough guess each index will be reaching 50-60GB in size.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here