Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

Interesting Error - Unable to Mount Exchange Databases

I recently began utilizing a Database Availability Group within my Exchange 2010 Mailbox servers. However, when I attempt to create a new mailbox database, I receive this message:

Exchange 2010 - Database Mount Error
I can see the database appear correctly FROM the mailbox server, where the database was created. However, when checking any other member of the DAG, I see a strange name. Here's what I see:

Database name, on the originating DAG server: "Test-SDUS"
Database name, on any other DAG member: "Mailbox Database 0085334295"

Let me know if you need any more info!

Best,
J
0
jmichaelpalermo4
Asked:
jmichaelpalermo4
  • 3
  • 2
2 Solutions
 
Jon BrelieSystem ArchitectCommented:
Are you able to mount it now?  I have to uncheck the mount database option when creating a new database, because it tries to mount it before it has completed creating it.
0
 
jmichaelpalermo4Author Commented:
Hmm - no go. Here's the error I receive when attempting to mount after it's been created

EMC DB Error
0
 
jmichaelpalermo4Author Commented:
Oh wow - after waiting a few minutes, everything looks good... I can mount the mailbox, then add it to the DAG members.

Is this normal? Or am I missing something, efficiency-wise in my Exchange setup.
0
 
Jon BrelieSystem ArchitectCommented:
First time I encountered it, I did some poking around and found the "wait 15-20 minutes" solution.  Usually I can mount it right away.  I think one time it took around 10 minutes.  Something to do with AD replication if I recall.
0
 
jmichaelpalermo4Author Commented:
Thank you! I appreciate your help :)
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now