|
|
Archiving can fail for any of the following reasons:
Configuration problems. Check through the Application Event Log to find out whether there are any messages there that help with solving the problem.
Communication or access problems. Check through the Application Event Log to find out whether there are any messages there that help with solving the problem.
There may be no archiving schedule set. If you have not set such a schedule, the Exchange Mailbox and Public Folder tasks do not run unless you use Run Now. Check the Application Event Log for entries made by the Exchange Mailbox task. Does archiving work when you use Run Now?
Try running the Exchange Mailbox or Public Folder task in report mode. This generates a report indicating what would be archived if you did a full run of the Exchange Mailbox task. The archiving criteria that you have set may not match the properties of any items in the enabled mailboxes or public folders.
No mailboxes have had archiving enabled. This does not apply to an Exchange Journaling task.
Use tracing so that you can follow the decisions made by the Exchange Mailbox or Journaling task.
If you have just started using Enterprise Vault, it may take several archiving runs before the system reaches a normal state. This is because a new installation may have more items to archive than can be processed in a single run of the Exchange Mailbox task. Enterprise Vault takes a few items from each mailbox and then, if there is still time in its schedule, goes around again to take more. So some items may have to wait for the next run of the Exchange Mailbox task.
This balancing process ensures that archiving is carried out evenly across all mailboxes. However, it can appear that Enterprise Vault is ignoring some items when, in fact, it is not.
Microsoft Exchange Server can monitor processes for you; see the Microsoft Exchange Server documentation.