adding database to exchange 2010 in DAG and moving mailboxes


I have two exchange 2010 servers in a DAG. I have six databases total. Four are replicated and each server has one that is not. I am able to create a new database even though I have 4 in a DAG and one additional totaling 5 on each server. I am running Exchange 2010 Std so I thought I was limited to 5 databases but I created a new database on each server without issue. I need to move all mailboxes on 2 of the DAG databases to new databases.

For example, one database is almost 200 GBs. So I guess I will need to add that much space, minus the white space (which I am not sure how much but know there has to be a good amount), just to move the mailboxes. Once I move them and confirm they are working, I was going to delete the old database to reclaim that space. Is this the correct way to do it? Do I need to add 200 GBs of storage just to move the mailboxes off of this one database?

sorry if this isn't detailed enough or states the wrong things - I am tired today ;-). Please feel free to ask questions and I will answer them or just tell or link me to what to do.

king daddyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
The database limit is five mounted databases per server.
Therefore if you create more than five databases in the DAG, then you will not get failover, because the databases cannot mount.

The easiest way to think of the DAG members is that the storage needs to be identical. Same layout, same space. The level of whitespace doesn't really come in to it, unless you are moving mailboxes in to a new database.

Otherwise what you have outlined is the correct way to do it. New database, add to the DAG, move the mailboxes in to the new database.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
king daddyAuthor Commented:
thanks Simon. should I suspend the replication as I move email accounts to the new database? Also, I am seeing msexchrepl 2153 and 4113 errors on this database and it is affecting user'e connections through outlook though webmail and mobile email work.
king daddyAuthor Commented:
also, I'm adding space to be able to move the mailboxes but then will delete a 200 GB EDB file, thus giving that drive 200 GBs free. I was trying to conserve space. Why even move mailboxes if I have the storage to add 200 GBs? I could just add 100 GBs and be set for a long time. Though, in this case, I am starting to receive msexchrepl 2153 and 4113 errors so it seems now it may be more than just a storage issue.

Thanks for your help
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Simon Butler (Sembee)ConsultantCommented:
I don't normally suspend replication during a move mailbox process because I want the content to replicate at the same time.

Error codes on their own aren't enough - however I suspect your storage may not be quick enough, or you have the logs and the database on the same spindles, meaning Exchange is writing to two locations at the same time.

king daddyAuthor Commented:
ok on the replication

I do have the db and logs on the same spindles. Though, these warnings and errors started intermittently one week ago today but the server has been in production with no changes for almost 3 years.

thanks for the input
Simon Butler (Sembee)ConsultantCommented:
Previous behaviour is not an indication that the server was setup correctly or that it will continue to work correctly.
If you have logs and the databases on the same spindles then the server hasn't been operating at optimum performance.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.