Forum Discussion

Fremont's avatar
Fremont
Level 5
9 years ago

Best Practice for Exchange 2010 journal mailboxes

Hi Guys,

Trying to understand what the best practice is for Exch. 2010 journal mailboxes.

Customer has 4 Exch. 2010 DAG-ed servers (Exch.1, 2, 3, 4) and 4 journal mailboxes.  They are doing journaling ONLY.  No mailbox archiving.

They have put all 4 journal mailboxes on a single Exchange server (Exch.4) and they have added Exch.4 server to the Exchange Server Targets container in EV.  Exch. 1, 2, 3 are NOT added.

QUESTIONS:

1. If one of the journal mailboxes fails over to any of the other 3 Exchange servers via DAG failover, will journaling continue to work? 

2. Do they need to add Exch.1,2,3 to the Targets container for point 1 above to work?

3. Anything else they need to do?

Thanks,

  • No, you will be fine.

    See 

    Enterprise Vault Journaling with Exchange Server 2010 DAG

    Problem

    Journal mailbox can be on a database being copied within a DAG in an Exchange 2010 environment.

    Solution

    If that is the case there is no need to create journaling tasks pointing to all DAG member servers, the one task is sufficient (the journal mailbox when created as a target is linked to a task and does not move on failover).

    Journaling should continue on failover of the DB. A small interruption of the journaling task could be observed if it is in the middle of processing a journal mailbox or message as it will receive an error from Exchange. This will result in a 1 minute pause of the task. After which the DB has successfully been mounted on another member of the DAG and the journal task will continue. The journal task really does not have any specific logic to continue (other than recreating MAPI sessions and re-opening the mailbox) as the Exchange Client Access Server (or array) and DAG handles the DB failover and makes sure MAPI traffic talks to the correct DAG member.

1 Reply

  • No, you will be fine.

    See 

    Enterprise Vault Journaling with Exchange Server 2010 DAG

    Problem

    Journal mailbox can be on a database being copied within a DAG in an Exchange 2010 environment.

    Solution

    If that is the case there is no need to create journaling tasks pointing to all DAG member servers, the one task is sufficient (the journal mailbox when created as a target is linked to a task and does not move on failover).

    Journaling should continue on failover of the DB. A small interruption of the journaling task could be observed if it is in the middle of processing a journal mailbox or message as it will receive an error from Exchange. This will result in a 1 minute pause of the task. After which the DB has successfully been mounted on another member of the DAG and the journal task will continue. The journal task really does not have any specific logic to continue (other than recreating MAPI sessions and re-opening the mailbox) as the Exchange Client Access Server (or array) and DAG handles the DB failover and makes sure MAPI traffic talks to the correct DAG member.