Who's Online
6 visitors online now
0 guests, 6 bots, 0 members
Support my Sponsor

In DAG, when Database moves host, eDiscovery fails

Have Exchange 2013 SP1 environment with 2 hosts running in a DAG hosting a database. Both hosts have CAS and Mailbox role installed in 2008 domain and have single namespace.

Have Node1 with few test mailboxes and Node 2 and created new database and moved all mailboxes including Arbitration mailboxes to this new database. Also added Node 2 as database copy for new database.

Users can send/receive mails and connect Outlook. Database failover from Node 1 to Node 2 is also working fine and users can connect normally.

The only thing isn’t working is eDiscovery which fails only when database is hosted on node 2. Searches are queued until the database is failed over to Node 1. Get-Mailbox -Arbitration shows that it is in DAG but attached to Node 1 and servername parameter as “Failed server”, which seems like arbitration mailboxes not failing over to Node2 as normal databases are. I shut down Node 1 to ensure that it’s only Node 2 hosting anything, but the arbitration and some mailboxes still show as Node 1.

Also ran Get-MailboxDatabaseCopyStatus | fl Name, index cmdlet to check if content index is healthy and found it to be healthy.

Solution:

Since the output for Get-Mailbox -Arbitration | fl Name, ServerName, Database pointed to a failed server, try moving the Arbitration mailboxes to another database on another running server.

And also eDiscovery fails only when the database is active on Node2, try reseeding of the database and check for the result for Get-Mailbox -Arbitration | fl Name, ServerName, Database which should be pointed to any node but not as failed server

Leave a Reply