The Exchange Journaling task runs continuously, checking for items in journal mailboxes and immediately archiving them. These items are deleted from the mailbox as they are archived and no shortcuts are created.

In the Exchange Journaling Policy the 'Return failed items to inbox' can be enabled so the Failed to Store folder will move the message back into the inbox to be reprocessed, this happens at task startup.

It is important to monitor the journal mailboxes to make sure that items are being archived promptly.  The following folders may also be created and may contain items.

 

Folder	Contents
Failed to store	Messages that could not be archived. They probably failed because of a problem with the Storage service. Move all these items back to the Inbox folder and the Exchange Journaling task will try again to archive them.
Failed to copy	Messages that are probably corrupt. Drag them to the desktop and then double-click on them. The message may now not be corrupt, in which case drag them from the Desktop to the Inbox folder and the Exchange Journaling task will try to archive them again. Remember to delete the corrupt versions from the Failed to copy folder.
Failed DL Expansion	Items that could not be archived because Enterprise Vault was unable to expand their distribution lists.
Failed Codepage nnn	Install the missing codepage or Use the default ANSI codepage (ACP codepage). When the codepage is correct, move the failed messages back to the Journal Inbox so they will be processed again.
Failed External Filter	Messages that could not be processes by a custom filter. Check the Enterprise Vault Event Log to determine the cause of the problem. Also check that the rule set file references the correct XML schema.

For more information on the Failed to... folders see the Administrators Guide.