Anyone Performance issue if setting the size of Vault cache very large?

[ECC1111]

Does anyone have experience on performance impact if the the size of Vault cache is too large? Our organization is going to deploy the EV soon. We will allow user to use Vault Cache. Will there be any performance impact (e.g. take long time to open the outlook? user need to wait for synchronization each morning?) if the Vault Cache is too large. Can anyone share your expereince ? Thanks.

[AndrewB]

you might want to have a look through this:

Virtual Vault Best Practices Guide

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

[Rob_Wilcox1]

How big is big?  And remember you can limit the size of Vault Cache as a %age of disk space, or a total amount of Gb..

There is also a rather odd Outlook registry key which can be implemented which compacts OSTs and PSTs on exit of Outlook (or is it startup?), and that can slow things down.

[ECC1111]

Most of our mailbox is over 8 GB. We prepare to let user have a 10GB vault cache which let user have similar experience as PST that they use too. I know vault cache is some how like an OST . We just want to have a better balance on the size and the performance.

[TonySterling · Accepted solution]

What version of EV?  If EV 9 make sure you roll out the latest client, there was an issue fixed in EV 9.0.4:

Vault Cache database files could grow very large, which affected Vault Cache performance [Ref 12918, E2554123]

In some circumstances, individual Vault Cache database files could grow very large, causing slow Vault Cache performance for users.

This has been fixed. Vault Cache database files should not now grow larger than the default size of 500 MB. Note that any existing large Vault Cache database files are not automatically resized.

[Rob_Wilcox1]

Good spot there Tony.  The issue/was that the trawler (which does the pre-emptive caching) wasn't really taking any notice of whether a DB file is/was 'full'.  So it just carried on adding data.

[ECC1111]

Thank you for sharing.