Video Screencast Help

Vault Store DB limitations on archived items

Created: 19 Apr 2013 • Updated: 23 Apr 2013 | 3 comments
superduper's picture
This issue has been solved. See solution.

Hi All

I believe in the performance guide for EV 7.5 there was mention of a suggested limitation of 100 million items per vault store db.

Does this still apply for later EV versions?

Is there any symantec best practises around this and how you would deal with a mailbox vault store? I.e. with journaling you can just create a new vault store & archive but its not that easy with user archives.


Operating Systems:

Comments 3 CommentsJump to latest comment

Advisor's picture

You can refer latest performance guides...

Symantec Enterprise Vault 10.0 Performance Guide

Symantec Enterprise Vault 9.0 Performance Guide

Symantec Enterprise Vault 8.0 Performance Guide

JesusWept3's picture

Honestly I don't think there are that many large organizations that will stick to those numbers because its impractical

I believe for peak performance though, it's a good number and does still apply just as long as you're aware that the bigger the DB the longer the backups and longer maintanance takes

So for some customers they never finish their maintanance routines because the indexes and tables are too big and then when indexes get too fragmented SQL starts doing full table scans and performance can go down hill quickly

Obviously with good sizing, not overloading a single vault store and things like storage expiry you shouldn't worry too much

Advisor's picture

In EV 10 SQL best practice guide, I see following:

The maximum number of items that may be stored in a single Vault Store database during its lifetime is 2,147,483,647. This includes items that have expired and are no longer in the database

Symantec Enterprise Vault 10.0: SQL Best Practices Guide