Description

With major changes introduced by Microsoft in Exchange 2013, many performance issues arose with both mailbox and journal archiving of Exchange 2013 by Enterprise Vault. These could manifest in many ways, including (but not limited to) any combination of the following:

• Archiving tasks throw 3419 errors connecting to Exchange 2013 targets, either frequently or very infrequently
• Slow archiving performance both for journals and user mailboxes
• Journal mailboxes building large backlogs of mail awaiting to be archived

A common benchmark for documenting the degraded performance is comparing archiving speeds targeting Exchange 2007 or 2010 against archiving speeds targeting Exchange 2013.  If an environment has both 2013 and a previous version stood-up and targeted for archiving, the performance disparity between the two can be substantial, even when archived by the same EV server(s). 

Note: Before making changes to Exchange 2013 or troubleshooting Exchange 2013 when new archiving performance issues arise after upgrading Exchange, be sure to gather and analyze dtraces of the relevant archiving tasks in Enterprise Vault.  Making the following adjustments is not advisable until it strongly appears that Enterprise Vault does not have any of its own internal delays or problems.

The following setting has been identified to allow more resources for Exchange 2013 clients' requests for database reading and writing; effectively improving archiving speeds and performance across several support cases with Veritas regarding Enterprise Vault archiving after upgrading Exchange to 2013. 

• Add the MailboxLockMaximumWaitCount key to the Microsoft.Exchange.Store.Worker.exe.config file

The config file to adjust is in the %Exchange Install Path%/bin directory on the mailbox server.  This is usually C:\Program Files\Microsoft\Exchange Server\V15\Bin. The key to add is MailboxLockMaximumWaitCount. The suggested value in terms of archiving performance is 20. This key controls how many queued mail database requests can "wait in line," and is set at 10 by default (if no key is present). This means that if there are 10 requests waiting to read and/or write to the mail store, and 11th would not be queued, but would be rejected.  These requests can include anything from regular Outlook clients, Enterprise Vault archiving, shortcut creation, etc. If one of Enterprise Vault's mail database read/write request is rejected, the task will throw a 3419.  If enough requests are rejected, the task will fail. 


By default, the config file likely appears like this:




Add these lines before the line in the file:

       
       
   


After adding, the config should look like this:



Adjusting this config file requires the store.exe process to be restarted to take effect, which can be done by restarting the Information Store service on the mailbox server.


If the Enterprise Vault configuration has been confirmed and optimized, and the above settings to do not improve archiving performance, Microsoft support should be engaged.

Note: Please refer to the Compatibility guide for supported versions. 

Exchange 2013 settings for improved archiving performance by Enterprise Vault