adding database to exchange 2010 in DAG and moving mailboxes
Greetings,
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.
THANKS A LOT!
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.
THANKS A LOT!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
Thanks for your help
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.
Simon.
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.
Simon.
ASKER
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
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
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.
Simon.
If you have logs and the databases on the same spindles then the server hasn't been operating at optimum performance.
Simon.
ASKER