Video Screencast Help

Scheduling Vault Cache Synchronization

Created: 12 Mar 2013 • Updated: 01 Apr 2013 | 5 comments
Abhijeet Kakade's picture
This issue has been solved. See solution.

The vault cache synchronizes every 24 hours since the last synchronization.

Is there a registry hack / setting that can be defined to modify this setting?

Version: EV 10.x

Outlook Version: 2010

 

Thanks in advance.

Operating Systems:

Comments 5 CommentsJump to latest comment

JesusWept3's picture

As far as I'm aware the only things you can do are minutes after a missed sync and minutes after opening outlook

The thing is, by default EV allows for 100 users to sync at the same time, and in a large environment with everyone syncing all the time, it may just cause even more sync slot full errors and warnings coming up

Advisor's picture

Yes you can use:  

OVMDCSyncFrequencyInSecs

Advisor's picture

How to implement:

OVMDCSyncFrequencyInSecs
This setting can be created in the following locations:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\VaultCacheStoreID
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client

DWORD: Number of seconds between scheduled synchronizations. The default
value is 86400, which is 24 hours.

Enables you to set the frequency of scheduled Vault Cache
synchronizations. The default value (86400 seconds) means that a
synchronization is initiated every 24 hours.
The new value only takes effect after the next scheduled synchronization.
The Outlook add-ins check for the setting as follows:
■ If the setting exists under \Client\VaultCacheStoreID, then that
value is used.
■ If the setting does not exist under \Client\VaultCacheStoreID,
then the \Client location is checked. If the setting exists there,
then that value is used.
■ If the setting does not exist in either location, then the default
value is used.
If you use a group policy to configure settings on users' computers,
then you can create the setting under \Client. Note however that a
value that is set under \Client\VaultCacheStoreID always takes
precedence.

I hope this helps..
Impact:

Each time a user synchronises there will be additional load placed on IIS to obtain a slot, SQL, to work out where the slot should be given, what permissions the user has, what items need to be uploaded, updated, downloaded, deleted, any folder hierarchy changes, retention category changes, and Enterprise Vault storage server, that has to interact with both IIS and SQL, whilst also servicing any requests for content resulting from this, and any other regular operations outside of this feature such as journal archiving, user retrieval/view requests, etc

Rob.Wilcox's picture

My question would be ...

Why do you want to change it?

Ben Heymink's picture

Unless there is a very good reason to change it, I wouldn't. It will put additional strain on the EV Server.

If there are a few users that are finding that they need more frequent synchronization because they are dragging items into Virtual Vault, consider using the threshold based archiving policy settings.

SOLUTION