Adding remote site exchange servers to exchange 2010 DAG
I currently have a DAG setup with 2 vm's at our main office. I am now going to setup two remote sites with their new exchange 2010 servers but just want to make sure on what I need to do.
We are going with one large DAG, and I want two copies of the db at each remote site and one copy from each remote back at the main site, so basically Active/Passive
So do I need to setup 2 vm's(exch 2010) at each remote site or just one, and do I need the CAS and Mailbox server roles at each remote site and do I need the hub transport at each remote site?
Any help with this would be greatly appreciated.
Thanks
We are going with one large DAG, and I want two copies of the db at each remote site and one copy from each remote back at the main site, so basically Active/Passive
So do I need to setup 2 vm's(exch 2010) at each remote site or just one, and do I need the CAS and Mailbox server roles at each remote site and do I need the hub transport at each remote site?
Any help with this would be greatly appreciated.
Thanks
ASKER
I already have the DAG group setup. My questions are pertaining to the remote sites with their new exchange servers to be added to the already created DAG
Hello,
Each DAG member is going to contain a copy of each database in the DAG. Your requirement for "two copies of the db at each remote site and one copy from each remote back at the main site" will not be possible if you have two DAG members at your main site as each would contain a copy of the database. Are your remote sites live sites or are they cold standby sites? If they are live sites, you should not be using "one big DAG". Each site should have its own DAG. If you use one DAG and you have a WAN connectivity issue, you will end up with a split brain scenario.
JJ
Each DAG member is going to contain a copy of each database in the DAG. Your requirement for "two copies of the db at each remote site and one copy from each remote back at the main site" will not be possible if you have two DAG members at your main site as each would contain a copy of the database. Are your remote sites live sites or are they cold standby sites? If they are live sites, you should not be using "one big DAG". Each site should have its own DAG. If you use one DAG and you have a WAN connectivity issue, you will end up with a split brain scenario.
JJ
ASKER
They are going to be live sites and I dont see this issue with having one big DAG because as I mentioned, each remote site will have 2 copies and one copy from each remote site will go to the main site.
Well, how is each remote site connecting to your Exchange cluster? Outlook Anywhere? If yes, then you don't need CAS/HUB roles. You can setup each remote site to use those roles and depending on your connection back to your primary site, it would make sense to have each site with all roles.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As stated above, 1 large DAG is not best practice if the other sites are live. At least the mailbox role should be at each site.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So if I go with the one DAG setup, do I need 2 exch 2010 in each remote site or just one?
The number of DAG members in each remote site will depend on what level of fault tolerance you want. If you want local fault tolerance, meaning if a server fails the databases won't fail over to another site, you will need two DAG members in each site.
JJ
JJ
ASKER
solved
http://technet.microsoft.com/en-us/library/ff622321.aspx