The solution is to specify the high usage mailbox as a Journal Mailbox.

Note: This procedure requires a slight modification to a SQL table.  Before running the query, perform a full backup of the EnterpriseVaultDirectory database

1. Disable the mailbox for archiving in the Admin Console

2. Follow the normal procedure to configure Journal Archiving

 - Create a Journal Archive

 - Create a Journal Task

 - Set the mailbox in question as a Journal Mailbox under Targets > Exchange > Journal Mailbox

3. Zap the mailbox using the steps outlined in Related Article: 000028255 

4. Run the Provisioning Task

5. Synchronize the mailbox through the Journal Task

6. Re-enable the mailbox for archiving via SQL.

 - Run the following in SQL to find the record relating to the mailbox:

Use EnterpriseVaultDirectory
Select * from ExchangeMailboxEntry where MbxAlias like '%[Mailbox Alias]%'

 7. To enable the mailbox,  run the following using information gathered from the previous query:

USE EnterpriseVaultDirectory
Update ExchangeMailboxEntry set MbxArchivingState = 1 where MbxAlias = '[Mailbox Alias]' and ExchangeMailboxEntryID = '[ExchangeMailboxEntryID from previous query]'

8. Restart the Journal Archiving task and monitor the mailbox to verify it is archiving. Note: it may take a while depending on the size of the mailbox

9. Export the old archive to a PST file and import it into the new Journal Archive

 

 

In some environments, a general catch all mailbox may be used for programs such as Jabber and Office Communicator. Depending on the volume of mail, the Mailbox archive task may not archive all content in a timely fashion such as a Journal task would therefore causing a large mailbox or other potential issues. An email administrator should consider configuring this scenario using a Journal mailbox, however in the case where this is not feasible, a work-around in EV can be done to allow this mailbox to be processed by a Journal task.