cancel
Showing results for 
Search instead for 
Did you mean: 

Journal Archiving and Exchange 2010 DAG

bteichner
Level 3

We are currently running Enterprise Vault against an Exchange 2010 DAG. We have two journal archive tasks that point to two separate journal mailboxes. The journal mailboxes are 95% of the time on a database that is active on our second mailbox server. In the case of a database failover to the primary mailbox server, the archiving tasks will not work since they are configured for the secondary mailbox server. What is the best approach for journal archive tasks and multiple DAG members, so that in the event of a database failover you can continue to archive the journal mailboxes? Can I have two additional journal archive tasks configured against the the primary server with the target as the same journal mailbox/archive, and just leave the task disabled until there is a failover?

1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

So the journal task should continue archiving the journal mailbox when it is on the other server.  You should see a message in the Event Logs letting you know there may be a performance hit as the journal mailbox is on the other server but it will carry on.

Are you seeing different behavior?

This is from the Enterprise Vault 9.0 Archiving from Exchange Server 2010 but still applies

Configuring Journal archiving tasks and targets should be approached differently. Journal archiving requires that a single target and task are created for each server within the Enterprise Vault console.

For example in the above scenario JournalDatabase1 is active on MailboxServer1, so only a single Journal Archiving Task for MailboxServer1 is required. In the event of a failover to MailboxServer3, the Client Access Server will automatically re-direct MAPI connections to the appropriate server where the database is now active. Enterprise Vault will log a warning event stating that a re-direct is occurring but archiving will continue as normal.

 

View solution in original post

2 REPLIES 2

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

So the journal task should continue archiving the journal mailbox when it is on the other server.  You should see a message in the Event Logs letting you know there may be a performance hit as the journal mailbox is on the other server but it will carry on.

Are you seeing different behavior?

This is from the Enterprise Vault 9.0 Archiving from Exchange Server 2010 but still applies

Configuring Journal archiving tasks and targets should be approached differently. Journal archiving requires that a single target and task are created for each server within the Enterprise Vault console.

For example in the above scenario JournalDatabase1 is active on MailboxServer1, so only a single Journal Archiving Task for MailboxServer1 is required. In the event of a failover to MailboxServer3, the Client Access Server will automatically re-direct MAPI connections to the appropriate server where the database is now active. Enterprise Vault will log a warning event stating that a re-direct is occurring but archiving will continue as normal.

 

bteichner
Level 3

Thanks for the clarification. We have maintenance planned for the DAG member that has the journal database/task on it, and I just wanted to figure out the best way to continue archiving before we shut the server down.