1. When do archiving runs start and stop?
Enterprise Vault initiates a run at the start of the scheduled archiving period, or each time “run now” is selected. Processing, including the start run event, normally starts shortly after this, but it may be delayed if there is a significant backlog of work already queued.
A scheduled run ends either when the end of the scheduled period is reached, or when archiving of the specified mailboxes has completed, whichever is sooner.
A run-now run ends when archiving has completed for the specified mailboxes .
2. Why do I have a lot of mailboxes in the “Partially Processed: pass limit reached” state or in the “Unprocessed Mailboxes” list?
The usual reason is that there is too much archiving to complete within the scheduled time window provided. Increase the time available in the schedule.
3. Why does mailbox archiving have multiple “passes”?
If Enterprise Vault attempted to completely archive a mailbox in one go then it would be possible for a small number of very large mailboxes to monopolize archiving until they completed, potentially leaving much smaller mailboxes unarchived. To prevent this the archiving agent is limited to archiving a restricted number of items in one pass before it relinquishes processing and allows another mailbox to be processed. By default this limit is 1000 items. Mailboxes which do not complete in a single pass will add an additional pass to the back of the archiving queue.
4. The report is showing a warning that a mailbox is not provisioned. How do I fix this?
The most likely reason is that the mailbox has been removed from a provisioning group by the Enterprise Vault administrator. To correct the problem, check the provisioning group of this user in the Administration Console.
5. The report is showing a warning that a mailbox is over the send-receive limit. How do I fix this?
When an Exchange mailbox is over a specified size limit it is no longer allowed to receive or send messages. This limit is defined by the Exchange administrator and is known as the send-receive limit. The Enterprise Vault archiving agent is also prevented from archiving the contents of a mailbox which is over its send-receive limit. There are two options to correct this warning:
a) Increase the send-receive limit for this mailbox. It may be possible to lower it again after archiving.
b) Delete (or move to PST) sufficient of the mailbox contents to bring the mailbox below the limit.
6. The report is showing a warning that a mailbox has not achieved quota. How do I fix this?
If a mailbox fails to achieve quota then this is probably because its contents conflict with the archiving policy. For example, a mailbox could contain a few very large messages which put it over the target quota. If the archiving policy specifies not to archive such large messages then these messages will not be archived and no amount of archiving will ever achieve quota.
To correct the problem, review the contents of the mailbox against the archiving policy. The full archiving report’s “Main Reason Items Not Archived” section indicates the likely reasons. Having identified the problem messages and policy settings, either remove the problem messages or change the appropriate policy settings.
7. Why does the Exchange archiving task produce different report results when run in report mode and in archiving mode?
There are some actions that the Exchange archiving task does not take when it is run in report mode:
- Custom filters that will apply when the Exchange archiving task runs in archiving mode are not taken into consideration when it runs in report only mode.
- If the provisioning group is configured such that an archiving run auto-enables provisioned mailboxes, they are enabled only when the Exchange archiving task runs in archiving mode. When run in report only mode, the report shows provisioned mailboxes with the status "No action taken. New mailbox". However, a subsequent archiving run will auto-enable then process the mailbox as normal.
8. Why is there no start of run event for the Exchange mailbox archiving task that is currently processing?
When scheduled runs of the Exchange mailbox archiving task start or restart, the task always writes a start of run message to the event log. However, run-now runs only write an event when they are first initiated. Any run-now run that is interrupted does not write another event when it is restarted. For example, this can happen when an Enterprise Vault server fails over to another node in a cluster and processing begins on the failover node.
This FAQ will be updated in the light of operational experience.