asked on How to setup a DAG in exch 2010 when servers are on different networks
We are trying to setup a DAG between 2 servers which are in the same domain, but on seperate networks.
The 2 servers are in sepreate locations also.
So for instance the 1 exch server has an IP address of 192.168.10.10 which is the IP range there for all of their servers, and the other exch server in the second location is on 10.0.0.5 along with all of its other servers.
So do I need to have the network IP addresss for the first nic to be the same for both servers and then the second nic which will be for the heartbeat for the DAG, also be the same IP address or do I have to setup the DAG with the 2 seperate IP addresses?
The 2 servers are in sepreate locations also.
So for instance the 1 exch server has an IP address of 192.168.10.10 which is the IP range there for all of their servers, and the other exch server in the second location is on 10.0.0.5 along with all of its other servers.
So do I need to have the network IP addresss for the first nic to be the same for both servers and then the second nic which will be for the heartbeat for the DAG, also be the same IP address or do I have to setup the DAG with the 2 seperate IP addresses?
Exchange
Last Comment
vmich
ASKER
Do you mean add the IP address via clicking on the properties of the DAG and add in both IP address from both exch servers like the 102.168.10.10 and the 10.0.0.5
Then add in the 2 servers after that?
Then add in the 2 servers after that?
ASKER
One other not also at the main site there is currently a DAG there but that is for the 2 in house exchange servers at the main office and they are also on the 192.168.10.10 network with a second nic for replication which is on 10.5.5.xxx
Then as I mentioned, this new DAG is for the dbs from the remote site to be replicated back to an exch server in the main office which this new exch server was built just for the new DAG for the remote site server
Then as I mentioned, this new DAG is for the dbs from the remote site to be replicated back to an exch server in the main office which this new exch server was built just for the new DAG for the remote site server
When you are configuring DAG it is recommended that you have a MAPI and a Replication network. This is so that you do not saturate your network during replication. This can happen if you have a large database and you need to reseed it to the passive DAG member, over the network, this can cripple your network.
You can get away without using a Replication NIC/Network configuration but i would not recommend this.
Will.
You can get away without using a Replication NIC/Network configuration but i would not recommend this.
Will.
ASKER
Ok I understand that the rep traffic should be separate from the regular network traffic, so with that in mind I guess I need to have and IP address on the remote server and one on the main office server which can communicate with each other. But they dont have to be on the same IP range (subnet) correct?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Well my issue is that both servers are on in the same domain, but the remote site has a different ip range than the main office where we setup another exchange server to be used for the remote copies from the remote server.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Ok I appreciate all of the input for this question but just want to make sure I got it correct..
So I would setup 2 nics on both servers, the one at the remote site and the one at the main site.
I would have an IP address for the the first nic at each site being on that sites (remote and main office) IP range and then the second nic would be have to be on the same IP address for both the remote and main office for the replication traffic, which would have the settings just for the ip and subnet and uncheck the register in DNS check box.
Do I have this correct?
So I would setup 2 nics on both servers, the one at the remote site and the one at the main site.
I would have an IP address for the the first nic at each site being on that sites (remote and main office) IP range and then the second nic would be have to be on the same IP address for both the remote and main office for the replication traffic, which would have the settings just for the ip and subnet and uncheck the register in DNS check box.
Do I have this correct?
That is correct. Because this is going over a WAN connection you are going to need to have routes in place so that the Replication NIC i.e. 192.168.0.1 is routing its traffic over the backup WAN connection, and vice versa.
As you have also stated you do not register these NIC's in DNS. In the event your Replication network is down or not reachable it will use the Production Network for replication (this is an automatic process, no configuration required)
Will.
As you have also stated you do not register these NIC's in DNS. In the event your Replication network is down or not reachable it will use the Production Network for replication (this is an automatic process, no configuration required)
Will.
ASKER
Wiil,
Question for you...
I have between the 2 networks the following ip range for the replication traffic: 192.36.12.xxx at the main site and 192.41.12.xxx at the remote site. Remember they are on the same domain just different subnets.
These are on the same vlan and the router allows these to communicate with each other so will this work for the rpelication traffic?
Question for you...
I have between the 2 networks the following ip range for the replication traffic: 192.36.12.xxx at the main site and 192.41.12.xxx at the remote site. Remember they are on the same domain just different subnets.
These are on the same vlan and the router allows these to communicate with each other so will this work for the rpelication traffic?
ASKER
Never mind, I answered my own question.... :)
:-)
Will.
Will.
ASKER
2 nics one for regular network and the other one at each site to its own replication network with communications setup between the 2 sites.
You will need an IP address for the DAG in each site though.
Simon.