Quantcast
Channel: Exchange Server 2013 - High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 1985

Configure DAG Replication Network

$
0
0

In my environment we had a 2 node DAG. We added a 3rd node in another site for site resilience. I configured the server adapters as follows: 

EXCServer01 with 10.10.10.70 MAPI/192.168.1.13 Replication

EXCServer02 with 10.10.10.71 MAPI/192.168.1.14 Replicaiton

DRServer with 10.60.10.55 MAPI/192.168.2.13 Replication

Configured static routes for the replication network. Ran on each server.

Netsh interface ipv4 add route 192.168.2.0/24 "Cluster Heartbeat" 192.168.1.254

Netsh interface ipv4 add route 192.168.1.0/24 "Cluster Heartbeat" 192.168.2.254

DAG Info

Name       : MapiDagNetwork
Subnets    : {{10.10.10.0/23,Up}, {10.60.10.0/23,Up}}
Interfaces : {{DRServer,Up,10.60.10.55}, {EXCServer01,Up,10.10.10.70}, {EXCServer02,Up,10.10.10.71}}

Name       : ReplicationDagNetwork01
Subnets    : {{192.168.2.0/24,Up}}
Interfaces : {{DRServer,Up,192.168.2.13}}

Name       : ReplicationDagNetwork02
Subnets    : {{192.168.1.0/24,Up}}
Interfaces : {{EXCServer01,Up,192.168.1.13}, {EXCServer02,Up,192.168.1.14}}

When I created a new databasecopy it appears the the database is being seeded over the MAPI network instead of the Replication network. Looking at my configuration is there anything that I've done wrong.


Viewing all articles
Browse latest Browse all 1985

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>