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?
LVL 1
vmichAsked:
Who is Participating?
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:
Unless there is a separate network connection between the two sites, I wouldn't bother with a heartbeat network. It is all going to get lumped in with everything else, so simply adds additional complexity.

You will need an IP address for the DAG in each site though.

Simon.
0
vmichAuthor Commented:
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?
0
vmichAuthor Commented:
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
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Will SzymkowskiSenior Solution ArchitectCommented:
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.
0
vmichAuthor Commented:
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?
0
Simon Butler (Sembee)ConsultantCommented:
Separating the replication and MAPI traffic is fine - but if there is a single wire between the two servers (typical single internet WAN connection) then how are you going to separate the traffic? You cannot, unless you start using QOS on the WAN link.

If you are going to have the two servers on their own network for replication, then they would be on the same subnet usually, BUT that depends on your routing configuration for that separate network.
It doesn't really have anything to do with Exchange at all!

Simon.
0
vmichAuthor Commented:
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.
0
Will SzymkowskiSenior Solution ArchitectCommented:
Depending on the company size and the severity you would have redundant WAN connections between sites even if this is a DSL connection it would still be recommended to do this.

Typically when you are using redundant connections like this you make use of them for backup/replication routines. This is so that the redundant connection is not just sitting there doing nothing.

This allows you to actually use it without affecting production.

Also as Simon mentioned you can also use QOS as well. Most business level and enterprise level appliances have this in place.

I just wanted to state this fact because if you have the infrastructure then it is worth implementing.

Will.
0

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
vmichAuthor Commented:
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?
0
Will SzymkowskiSenior Solution ArchitectCommented:
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.
0
vmichAuthor Commented:
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?
0
vmichAuthor Commented:
Never mind, I answered my own question.... :)
0
Will SzymkowskiSenior Solution ArchitectCommented:
:-)

Will.
0
vmichAuthor Commented:
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.
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.