Skip to main content

360 ICT, reliability guaranteed

Maximum number of Exchange Databases reached

So we have an highly available Exchange environment with multi-tenantcy configured. This would seem a bit much wiht only ~20 employees, but we did this to get some hands-on experience with Exchange 2013 and 2016 with the multi-tenancy setup. We’ve been running multi-tenancy setups since exchange 2007 and it has had some major overhauls. Exchange 2010 had a MS program HMC for which you needed to certify and I believe (the links are all dead now) it had something of 11 servers minimum with SQL servers for the GAL lists. Since 2013 this (thank god) has become much easier.

But we had some connectivity issues after one of the servers rebooted and we found in our eventlog:

database copy ‘MDB04’ on this server wasn’t able to mount because the number of mailbox database copies on this server exceeds the configured limit. The error returned was “Couldn’t perform the database failover.

First we thought we didn’t have loaded the correct license, but the ecp showed a enterprise license installed.

Getting the mailbox server details with

get-mailboxserver -Identity SERVERNAME |fl

showed us a default of 1 Active mailbox:

Its on the line that says:

MaximumActiveDatabases

So fixing this on both servers with

set-MailboxServer -identity SERVERNAME -MaximumActiveDatabases 10

fixed the problem for us.

 

Request Information

Do you want to know more about Maximum number of Exchange Databases reached? Easily request more information.

More Blog Items