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...

If you have storage expiry enabled, and you have enabled the Expiry Report button in Outlook, end users can click on the button and get a "live view" of what data is about to be expired from Enterprise Vault.

The way that this works is that the button in Outlook makes a call to searcho2k.asp, passing a parameter to indicate that you want to receive the Expiry Report (rather than the more normal "integrated search" web page).  On the server side of things, the index for the users archive is queried for items which are about to expire (based on retention category etc) and then the results returned to the client.  Remember that you can set expiry based on archived date or modified date (the default being archived date).

This is what the request looks like when it comes on to the Enterprise Vault Server :

2011-03-29 09:14:19 192.168.1.2 GET /EnterpriseVault/searcho2k.asp server=...

Please access my blog at 

http://barneyhaye.typepad.com/blog/

As a good practice to follow, it is an idea to export the contents of the IIS Metabase before making significant changes to IIS configuration.  Especially if it's "several" changes, that you're likely to forget about within 5 minutes of making them!

To export the metabase follow these simple steps you can backup/restore the whole configuration by opening IIS Manager, and right clicking on the server name and choosing "All Tasks" -> "Backup/Restore Configuration" :

You can also export just the web sites by right clicking on the Web Sites node, and choosing “All Tasks” –> “Save Configuration to a File” :

This puts the configuration out to an XML file, that you can specify, and optionally...