Installing a new exchange 2013 in the company
Dear All
I currently have a physical server with server 2008 R2 running exchange 2013 cu15, with build no 15.0.12635, and I see the database size is quite large, and I'm planning to install one more exchange server 2013 with mailbox and client access roles installed, since I want to create a new database in this new server so that I can move some of the mailboxes in the old server to this new server, may I know how can I achieve this ? Is it correct to install CAS & mailbox roles in the new server and move mailbox to new database ? Any help would be appreciated!
Keith
I currently have a physical server with server 2008 R2 running exchange 2013 cu15, with build no 15.0.12635, and I see the database size is quite large, and I'm planning to install one more exchange server 2013 with mailbox and client access roles installed, since I want to create a new database in this new server so that I can move some of the mailboxes in the old server to this new server, may I know how can I achieve this ? Is it correct to install CAS & mailbox roles in the new server and move mailbox to new database ? Any help would be appreciated!
Keith
The above comment is not correct. A bottleneck is NOT created. In fact, it will open things up as you will have two servers using the CAS role.
When you set up your new Exchange server you can create a DAG so that you will have high availability, if that is something you are looking for.
http://www.mustbegeek.com/configure-dag-in-exchange-2013/
All you will need to do is set up your second server in your environment, and move your mailboxes.
I have many customers who have a setup similar to the one you are proposing and everything works fine.
Just make sure you have good backups incase there is a disaster. With good backups, restores aren't that difficult.
When you set up your new Exchange server you can create a DAG so that you will have high availability, if that is something you are looking for.
http://www.mustbegeek.com/configure-dag-in-exchange-2013/
All you will need to do is set up your second server in your environment, and move your mailboxes.
I have many customers who have a setup similar to the one you are proposing and everything works fine.
Just make sure you have good backups incase there is a disaster. With good backups, restores aren't that difficult.
ASKER
Can I not to use DAG, as I have limited hardware resources, I just want to build one more server to create a new mail database and move some of the mailboxes to the new server, can I achieve it in this way ?
Hi,
I would like to stay with my previous comment even Scott may disagree.
From your post it states you suffer from big databases, bringing a dag to the picture will bring 2 big databases.
Again, Yes you can use this approach but you have to make sure you have solid backup plans.
It can occur that one mail server dies on you while running a weekly backup (for instance) which makes it necesarry to restore.
If you made structural changes to the exchange setup in the meanwhile it is possible the coexcistance gets corrupted, hence the big advantage of a dag.
So in case of disaster make sure you can rebuild the coexcistance and restore the complete database or on a mailbox level.
I would like to stay with my previous comment even Scott may disagree.
From your post it states you suffer from big databases, bringing a dag to the picture will bring 2 big databases.
Again, Yes you can use this approach but you have to make sure you have solid backup plans.
It can occur that one mail server dies on you while running a weekly backup (for instance) which makes it necesarry to restore.
If you made structural changes to the exchange setup in the meanwhile it is possible the coexcistance gets corrupted, hence the big advantage of a dag.
So in case of disaster make sure you can rebuild the coexcistance and restore the complete database or on a mailbox level.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
May I know how to run the exchange health check ?
Run
Test-ServiceHealth
In the exchange powershell and watch for services NOT running. Or
Get-Queue | Select Identity,Status,MessageCou
To monitor if your server is not creating big queues.
Test-ServiceHealth
In the exchange powershell and watch for services NOT running. Or
Get-Queue | Select Identity,Status,MessageCou
To monitor if your server is not creating big queues.
My apologies. I thought I put a link in. This script is awesome.
https://practical365.com/blog/test-exchangeserverhealth-ps1-v1-06-now-available/
https://practical365.com/blog/test-exchangeserverhealth-ps1-v1-06-now-available/
ASKER
Thx for your useful information, so for the new exchange that I'm going to setup for creating new mail database, I need to install CAS n mailbox role for this server ? And for the send connector what should I put ? And for smart host I should enter the other exchange server IP am I correct ?
ASKER
Great
Yes, you need to install the CAS mailbox role.
You shouldn't need another send connector.
You also shouldn't need to enter smarthost information. All of that should be picked up from the other server.
Glad I could help.
You shouldn't need another send connector.
You also shouldn't need to enter smarthost information. All of that should be picked up from the other server.
Glad I could help.
Your approach is right but also wrong.
Yes you can create a new server with a new database to balance the hdd load but you are creating a bottleneck.
Both servers can coexcist but in case off disaster, if one mailserver breaks it can be difficult to restore.
Wouldnt it be more smart to add more storage to the excisting exchange server and create a secondairy database on that machine?
Cheers