Forum Discussion

Robert_Ton's avatar
Robert_Ton
Level 5
14 years ago

Scheduled Archiving Run for Exchange - Quick Question

When a scheduled run kicks off on an Exchange Server, does it process every mailbox, and then if it has time, repeats that process and goes through the mailboxes again? In our new Exchange 2010 environment, that looks like what I'm seeing.

We are running EV 9 SP2.

Thanks.

  • What happens is when the schedule kicks off it posts a message to process all mailboxes that are provisioned and enabled on that exchange server, after that message is posted, it will then post a bunch of Process Mailbox messages in the exchanges A5 queue.

    It will then go through and archive the amount of items in the Message Per Pass which is set in the mailbox archiving policy, so for instance its default is 1000 items, so it will archive 1000 items in each mailbox (if there is that many to archive) and then after 1000 it will go to the next mailbox.

    EV will keep a track of how many mailboxes have more than 1000 items to process and once the queue is cleared it will then re-queue those mailboxes to process again and ignore the ones that have processed fully

    So if you have say 1000 messages per pass and you have 30 mailboxes in total,
    10 of them have 800 messages, 10 have 1500 messages and the other 10 has 2500 messages

    First Pass, all thirty are queued. 10 complete with all their messages being archived
    Second Pass, only the twenty are requeued, the next 10 will complete with all their messages being archived (As they only have 500 left)
    Third Pass, only ten mailboxes are re-queued as they now have 500 messages left to archive

    This is why if you have a 24x7 schedule set that this is bad, because once it gets through all the mailboxes and all the messages, they won't be requeued until the schedule is stopped and started again, so you would be best off putting in 15 minute intervals every 4 hours or so if you really wanted to have a 24x7 archiving policy

3 Replies

  • What happens is when the schedule kicks off it posts a message to process all mailboxes that are provisioned and enabled on that exchange server, after that message is posted, it will then post a bunch of Process Mailbox messages in the exchanges A5 queue.

    It will then go through and archive the amount of items in the Message Per Pass which is set in the mailbox archiving policy, so for instance its default is 1000 items, so it will archive 1000 items in each mailbox (if there is that many to archive) and then after 1000 it will go to the next mailbox.

    EV will keep a track of how many mailboxes have more than 1000 items to process and once the queue is cleared it will then re-queue those mailboxes to process again and ignore the ones that have processed fully

    So if you have say 1000 messages per pass and you have 30 mailboxes in total,
    10 of them have 800 messages, 10 have 1500 messages and the other 10 has 2500 messages

    First Pass, all thirty are queued. 10 complete with all their messages being archived
    Second Pass, only the twenty are requeued, the next 10 will complete with all their messages being archived (As they only have 500 left)
    Third Pass, only ten mailboxes are re-queued as they now have 500 messages left to archive

    This is why if you have a 24x7 schedule set that this is bad, because once it gets through all the mailboxes and all the messages, they won't be requeued until the schedule is stopped and started again, so you would be best off putting in 15 minute intervals every 4 hours or so if you really wanted to have a 24x7 archiving policy

  • That makes sense - we haven't run into this much due to the large number of mailboxes we have in Exchange 2007. But since we have so few mailboxes on 2010, I'm seeing what you describe.

    I should have mentioned we do quota based archiving...I assume it behaves the same way.

    Thanks for the quick reply.

  • yeah the exact same , if it knows it has more to archive, it will re-queue them
    What you should do is check the time stamps of the messages in the queue

    If your archiving window starts at Midnight and the earliest item is at 1:43am then this would suggest a re-queue, if the earliest item is at 12:01AM then it would suggest its not getting through your entire set of mailboxes enabled for archiving and be indicative of a bigger problem