Link to home
Start Free TrialLog in
Avatar of CISS
CISSFlag for United States of America

asked on

Exchange 2013 flailing default database, question re system mailboxes

We have a single exchange 2013 server that started with a single default database (DB01). We've had corruption issues on that database and have moved all the user mailboxes to a second database (DB02). For the last few days, DB01 has been finding corruption while indexing, dismounting DB01, creating a new instance of the database and running for a bit until it hits corruption, then repeating the cycle.

This cycle started a few days ago when there were still several mailboxes on DB01. I disabled them and recreated them on DB02. All user mailboxes are now on DB02 but DB01 could not be reached, so it may still see them as active on DB01. Not sure if that is relevant.

Exchange seems to be working ok for users other than the public folder calendar being unavailable. Flailing DB01 shows as mounted in ECP but with content index failed.

The real question is what is to be done about the system mailboxes still on DB01 if I can't connect to them to move them? Can they be manually recreated on DB02? What are the options if the default database with all the system mailboxes become unavailable?

Thanks for any assistance.
ASKER CERTIFIED SOLUTION
Avatar of M A
M A
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of CISS

ASKER

thanks. Does that require dismounting the flailing DB01? How does setup /prepareAD know to put the system databases on DB02? Does that need to be specified somewhere.

If I dismount DB01, will exchange continue to work? I can't tell if exchange is accessing those system mailboxes enough to keep going as that database goes up and down or if they just aren't needed short term
After running the command successfully run this command to see where it is created.
get-mailbox -arbitration | fl name,database
Avatar of CISS

ASKER

thanks. I'll run this over the weekend
Avatar of CISS

ASKER

I ran the commands above and also those in the jaapwesselius link. Those all succeeded. I did have to add the migration mailbox back in but I found 2 commands for that, ran them,  and am no longer getting the error in EAC about not having a migration mailbox.

I saw elsewhere that the system mailbox starting in eodc1c29 is a discovery mailbox. That one is enabled. In the original setup that got corrupted, we had a "Discovery Search Mailbox" that began with {D9a9.....}. I had deleted all the system mailboxes, including this one, from ADUC. the /prepareAD added this discovery search mailbox back into ADUC. I'm guessing this is a mailbox that I should also enable, is that correct? Is there a specific command for that? I have the command I used to enable the migration mailbox but I don't know if just modifying that one is the way to go

thanks for all the help. I must not have been googling how to get to all this information correctly. So far, so good. Hopefully, almost done.
Avatar of CISS

ASKER

This procedure worked. Only part unresolved is a discovery search mailbox that appeared in active directory and I'm not sure how to add it but exchange seems to be working normally without it.