Archiving and journaling performance affected on Exchange 2013

Article: 100015873
Last Published: 2021-10-01
Ratings: 0 0
Product(s): Enterprise Vault

Problem

Enterprise Vault uses restricted views to query Exchange to determine what messages are eligible for archiving/journaling. In Exchange 2010 and earlier, repeated queries against the same folder (in the case of Journal Archiving, the Inbox) executed quickly because Exchange cached the results of the restricted view queries.  On Exchange 2013, these queries no longer appear to be cached.

 

Error Message


Dtrace the archiving/journaling task In order to determine if the problem is occurring. The below line indicates a delay in returning results of items eligible for archiving/journaling.   

{CArchivingAgent::processMessages:#5012} It took [482.298065] seconds to query rows of folder [Inbox].  returned [676] of max [1000] rows requested.

In some cases, MAPI timeouts (error code 0x80040401) may be seen.

{CJournalPart::MakeJournalPartMsg} HRXEX fn trace : Error [0x80040401],
{CArchivingAgent::isEligibleForArchive:#4749} An error occured hence this message will be ignored.UserMailbox=[/O=[ORG UNIT]/OU=EXCHANGE ADMINISTRATIVE
GROUP ([GROUP NAME])/CN=RECIPIENTS/CN=JOURNAL] MsgTitle= [MM notification] Hr=[0x80040401]

 

Cause

Microsoft may have identified the root cause as being the result of a change made in Exchange 2013 whereby queries against the same folder are no longer cached. Any application making use of this form of query will be impacted, potentially reducing the efficiency of these calls and having an impact on performance. (See https://support.microsoft.com/en-us/kb/3077710 for further details).

The alternative solution detailed in KB3077710 to use search folders has not yet been validated by Veritas engineering and investigations continue.

When designing Exchange 2013 solutions it is recommended to refer to the latest Enterprise Vault Performance Guide.

Enterprise Vault 11.0.1 shipped with a new high performance and scalable journaling solution. All Enterprise Vault customers are advised to consider moving their journaling solution to Enterprise Vault’s SMTP Journaling capability. SMTP Journaling is not affected by this issue.

For more information on SMTP Journaling review the digest: Enterprise Vault SMTP Archiving: key topics

 

Solution

This issue has been addressed in the following release:
 
Enterprise Vault 11.0.1 Cumulative Hotfix 4 Release
https://www.veritas.com/docs/000097959

References

Etrack : 3820305

Was this content helpful?