Unmounted DB

Exchange 2013 SP1 with 2 member server 1 DAG. At the present time, 1 of the DAG members is down. The 2nd member switched to active but the DB is not mounted therefore no email is flowing. I try to mount the DB in ECP and recieve:

How can i mount the DB on the second member server?

July 6th, 2015 10:00pm

Try mounting it using the shell, add the -Verbose parameter, and see if you get any additional information.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 10:03pm

Try mounting it using the shell, add the -Verbose parameter, and see if you get any additional in
July 6th, 2015 10:28pm

You can reseed it from the good copy...

http://exchangeserverpro.com/how-to-reseed-a-failed-database-copy-in-exchange-server-2013/

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 10:35pm

Agreed, and if you need to rebuild the server, just use setup /RecoverServer.  It'll reinstall based on the settings of the original stored in Active Directory.
July 6th, 2015 11:19pm

Well, the DB seems to get dismounted every-so-often. Here is the error when trying to mount the DB:

One of the other member servers is down at the moment but i thought the other member would pickup and mail flow would continue.

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 8:39am

Seems i should run:

Move-ActiveMailboxDatabase database1 -ActivateOnServer dagnode2 -SkipHealthChecks -SkipActiveCopyChecks -SkipClientExperienceChecks -SkipLagChecks -MountDialOverride:BESTEFFORT

Is this recommended when one of the member servers has suffered a storage failure and may be down for a day or 2?


  • Edited by forgiven 18 hours 14 minutes ago
July 7th, 2015 9:13am

Anyone have any advice they can share?
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 9:53am

That command is fine if you're willing to accept data loss.

As to your earlier post, that error often means that there is some sort of network problem between the nodes.  A failed node could cause that, I guess.

July 7th, 2015 10:08am

That command is fine if you're willing to accept data loss.

As to your earlier post, that error often means that there is some sort of network problem between the nodes.  A failed node could cause that, I guess.

No, would like to not have any data loss. So the other server had 2 failed drives on the RAID 5 array. I am working with Dell to see if we can rebuild the array. In the meantime, i need the second member server to stay up and accept email. Seems it does not want to do that. So i was trying to find a way to "force" the other working member server to continue email flow. Basically, the failover did not work and i am trying to restore email flow with the working member server. Any ideas?

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 1:06pm

I strongly recommend you open a ticket with Microsoft Support, or hire an experienced consultant to come in.  Your problems are way too complicated and time-sensitive for a forum such as this to be of effective help.

July 7th, 2015 3:34pm

I strongly recommend you open a ticket with Microsoft Support, or hire an experienced consultant to come in.  Your problems are way too complicated and time-sensitive for a forum such as this to be of effective help.

I hear what you are saying but i only need the second server to do what it was made/configured to do. I dont think i need someone hired or MS support to do that? These servers were setup in a redundant manner for exactly this type of thing. I was thinking some command needed to be run to tell the second working member server to assume all control and that the other member server was "offline".

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 3:45pm

It would appear that you weren't as redundant as you thought you were.

You have to point DNS to it if you don't have working load balancing.

If mail is not flowing, it could be that all connectors are configured on the down server.  You can try removing the down server from all connectors, adding the up server to them if necessary, and then try resubmitting any messages that are being held.

On the inbound side, make sure MX records, hygiene appliances or services, and/or NAT mappings point to the up server.

July 7th, 2015 3:50pm

It would appear that you weren't as redundant as you thought you were.

You have to point DNS to it if you don't have working load balancing.

If mail is not flowing, it could be that all connectors are configured on the down server.  You can try removing the down server from all connectors, adding the up server to them if necessary, and then try resubmitting any messages that are being held.

On the inbound side, make sure MX records, hygiene appliances or services, and/or NAT mappings point to the up s

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 4:23pm

That'll do it.  Glad you got it sorted.
July 7th, 2015 4:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics