Video Screencast Help
Archiving and eDiscovery Community Blog
Showing posts tagged with Enterprise Vault
Showing posts in English
Rob.Wilcox | 04 Apr 2011 | 0 comments


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

Rob.Wilcox | 31 Mar 2011 | 1 comment


Today, March 31st, has been declared World Backup Day.


When did you last do it?

Rob.Wilcox | 29 Mar 2011 | 0 comments


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 GET /EnterpriseVault/searcho2k.asp server=...

Rob.Wilcox | 29 Mar 2011 | 0 comments


One of the interesting things in Exchange 2010 is the Throttling Policies which Microsoft have introduced.  In Enterprise Vault we have a script with instructions which adds an unlimited/unrestricted policy and puts the task service account/mailbox into that policy.  But what does it look like on startup?


45313:46:40.332 [6448](ArchiveTask)<9708>EV:LCExchangeVersion::IsExchange2010orAbove (Entry) |

45413:46:40.332 [6448](ArchiveTask)<9708>EV:MCExchangeVersion::IsExchange2010orAbove|CExchangeVersion::IsExchange2010orAbove - Valid: [TRUE]

45513:46:40.332 [6448](ArchiveTask)<9708>EV:MCExchangeVersion::IsExchange2010orAbove (Exit) |Success  [0] |

45613:46:40.332 [6448](ArchiveTask)<9708>EV:MCAgentTask::CheckRunningAccountForMailbox - Executing query ((&(objectCategory=person)(|(&(msExchVersion<=2251799813685248)(!(msExchVersion=2251799813685248)))(!(...

Rob.Wilcox | 24 Mar 2011 | 4 comments


An old, old “bug” has been addressed in the upcoming release of Enterprise Vault 9.0.2.  When exporting an archive to PST, you could specify a size limit for the file bigger than 1.5-1.8 Gb.


Now you can !


Before :

After :


You can now go up to 20 Gb for a Unicode PST, 1.5 Gb for the old-school “2Gb max” ANSI PST.  And yes, it works.

Here is a nice picture of two exports of the same archive ..  One where I picked 2.2 Gb for the size, and one where I picked 3.6 Gb for the size of each PST :

Rob.Wilcox | 24 Mar 2011 | 0 comments


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

Rob.Wilcox | 22 Mar 2011 | 0 comments


A colleague of mine contacted me the other day and offered to create an "official" article to describe the issues that some people have encountered with PSTDisableGrow since using the Enterprise Vault 9.0.1 Outlook Addin.


The article is here :


For those who are watching .. it's also described "properly" in the EV 9.0.2 documentation.

Rob.Wilcox | 18 Mar 2011 | 0 comments


When setting up Vault Cache you can indicate the size of the cache that you want to allow on end-users workstations.  Picking the number is a balance between space consumed on the workstation, space available, amount of impact you want to have on the EV server in order to build the data, and the ongoing load on the EV server keeping the data up to date, and retrieving missing data when a user requests it.

As described previously, the Vault Cache consists of :

a/ A metadata cache

b/ Archived content (cache, I guess)

The size that you set in the policy, or override on a per workstation basis, is the total of these two aspects.  There is one caveat though.  Your MDC will always be downloaded, full fidelity.  What that means is described in the examples below :

If you limit the size to 2 Gb, and your MDC file is 250 Mb, then you can have up to 1750 Mb of archived content.

If you limit the size to 2 Gb, and your...

Rob.Wilcox | 18 Mar 2011 | 0 comments


A question I was asked the other day was whether I can have Virtual Vault in the Enterpris Vault Outlook world, without any archived content on the end-users workstation.

The answer is yes..  Nearly :)

Vault Cache consists of two components :

a/ A metadata cache

b/ Archived content (cache, I guess)

Whether the users desktop policy says to have content or not, you always have the metadata cache for each archive that you synchronise.  This is seen on the client as one (or more) .MDC files.

You can't get away from having that.  If you delete it, next time Outlook starts you will get a new one (placing a burden on the Enterprise Vault server hosting your archive) and until that MDC is built on the client, the contents of Virtual Vault (even the hierarchy) will be incomplete.

So that's why I say "yes"... nearly :)