• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Apr 042011

A few weeks ago a colleague asked what was “included” in the OVStoreSize calculations.  On the Enterprise Vault Outlook client, Vault Cache consists of largely two components :

* Metadata cache

* Content cache

You always get the metadata cache – one per archive that you are synchronising with.  The Content Cache is dependent on policy.  As an Enterprise Vault Administrator you can specify the maximum size of the Vault Cache, using the registry key OVStoreSize (on each client) or the policy setting.  Users can also configure the maximum size by going in to the properties for Vault Cache once setup (from the Tools menu in Outlook)

In the users Desktop Policy you can see the setting for the size allowed :


You can see it can be based on a hard-maximum or a percentage of free space at the time of setting up the cache.

Contents of folder :


In the above screenshot you can see I’ve got a number of .db files, that’s the Content Cache part of Vault Cache, and one .MDC file, that’s the metadata cache part of Vault Cache.


What’s included?

If you specify a limit of 2 Gb for the size of the cache, then you will get the Metadata Cache file, and any remaining space will contain Content .db files.  You will always get the Metadata cache though, regardless of the size defined.  Here are some examples:

Size = 2 Gb

Metadata cache is 1.25 Gb

Content will be about 750 Mb


Size = 2Gb

Metadata cache is 2.5 Gb

No content will be stored


So it is worth bearing in mind that if you set the value of the cache size to be very low, or even a percentage of disk space, a client machine might still use up more space than that.

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>