Exchange Journaling task queues

Table: Exchange Journaling task queues describes the queues that the Exchange Journaling task uses. Here, exchange server is the name of the server being managed by the Exchange Journaling task, whereas number is a number that uniquely identifies the queue.

Table: Exchange Journaling task queues

Queue name

Messages placed on the queue

Enterprise Vault Journaling task for server queue J1

Post Process Archived Item, Operation Failed.

Enterprise Vault Journaling task for server queue J2

Process Item.

Enterprise Vault Journaling task for server queue J3

Process Mailbox.

Enterprise Vault Journaling task for server queue J4

Synchronize System.

Table: Messages in the Exchange Journaling task queues provides more information on the messages that the Exchange Journaling task may place in queues J1 through J4.

Table: Messages in the Exchange Journaling task queues

Message

Notes

Operation Failed

Informs the Exchange Journaling task that an error has occurred and that it should do the following:

  • Change the message from archive pending back into a message. The message will be reprocessed later.

  • Move the message to the Failed to Store folder.

This message is sent if an error occurs during archiving and storage.

Post Process Archived Item

Informs the Exchange Journaling task to delete an archive pending item from the journal mailbox. It occurs after a message has been stored by the Storage service, and backed-up.

Process Mailbox

Asks the Exchange Journaling task to examine the journal mailbox, finding any messages that have arrived. Up to 500 new messages will be turned into archive pending, and a message is placed on the Storage Archive queue of the Storage service for each message to be archived.

The process mailbox message is issued every minute onto queue J3. This allows for continuous scanning of the journal mailbox while the Journaling task is running.

Synchronize System

Synchronization requests for an Exchange Journaling task are placed on the J4 queue. When synchronization is run, a Synchronize System request is placed on this queue, and this generates a Synchronize Mailbox request for each mailbox that needs to be synchronized. Having multiple Synchronize Mailbox requests means that the requests can be serviced by multiple threads.

The J4 queue is processed at all times but is always the lowest priority task. This means that scheduled background archives always take precedence over a synchronize.