Exchange Server 2016 standalone deployment/coexistence Deployment (v)--Configuring Dags (bottom)

Previous we created the server configuration for the DAG, and then we'll talk about the configuration of the DAG replication network.

First, we need to add a second NIC on two Exchange 2016 servers, which will be the exclusive network segment that our DAG replicates. The benefit is that Exchange 2016 normal external server data requests and back-end mailbox database data are replicated into two network segments.

This allows the transmission efficiency and replication efficiency to be ensured in the case of non-interference.

The following actions need to be done on the DAG member server. Our environment here is just two exchange 2016 built.

We can differentiate two NICs from the name, LAN is responsible for external mail service, and DAG is the exclusive database replication network

650) this.width=650; "Width=" 679 "height=" 193 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/7D/2F/ Wkiol1bihmpjn0cqaachy7u2toi296.png "border=" 0 "/>

Next, we'll configure the DAG Nic by following

650) this.width=650; "width=" 377 "height=" 474 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/7D/30/ Wkiol1bihmsgrzdoaabo1munc-m292.png "border=" 0 "/>

Manually configure a separate private network segment to be provided to the DAG network.

650) this.width=650; "Width=" 415 "height=" 464 "title=" clip_image001 "style=" border-top-width:0px;border-right-width : 0px;border-bottom-width:0px; "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/M02/7D/30/ Wkiol1bihmxaygqsaabec_pty0k339.png "border=" 0 "/>

650) this.width=650; "width=" 413 "height=" 495 "title=" clip_image002 "style=" border-top-width:0px;border-right-width : 0px;border-bottom-width:0px; "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M00/7D/30/ Wkiol1bihmbd-ftaaabbn1y0huc707.png "border=" 0 "/>

After the configuration is complete, in Network Connection Manager, select Advanced Settings

650) this.width=650; "Width=" 571 "height=" 225 "title=" clip_image001[5] "style=" border-top-width:0px; border-right-width:0px;border-bottom-width:0px; "alt=" clip_image001[5] "src=" http://s3.51cto.com/wyfs02/M01/7D/ 31/wkiom1bihelznvfsaablj2jagxm086.png "border=" 0 "/>

Manually move the production NIC to the top of the LAN, so that it takes precedence over its network connection.

650) this.width=650; "Width=" 416 "height=" 465 "title=" clip_image002[5] "style=" border-top-width:0px; border-right-width:0px;border-bottom-width:0px; "alt=" clip_image002[5] "src=" http://s3.51cto.com/wyfs02/M02/7D/ 31/wkiom1bihekashscaabe5katjs0051.png "border=" 0 "/>

Once added, test the private DAG network for connectivity

650) this.width=650; "width=" 497 "height=" 398 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/7D/30/ Wkiol1bihmit-tjiaabkpuho378018.png "border=" 0 "/>

Click Add Dag Network

650) this.width=650; "Width=" 864 "height=" 279 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/7D/30/ Wkiol1bihmqgqqfqaaduxwimphm556.png "border=" 0 "/>

DAG Replication Network configuration is simple, after entering the replication network name, add the DAG private subnet segment, the system will automatically identify the network segment of the two DAG network card IP, tick the bottom of the "Start Replication", click Save.

650) this.width=650; "Width=" 518 "height=" 726 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/7D/31/wKiom1biHEWCECMlAAA_ Kfulm4m361.png "border=" 0 "/>

At this time, we can see that there are two network groups on the right, one is the system default Mapidagnetwork group, and one is created by us.

This time, manually click the "Disable Replication" button in the first Network group to turn off DAG replication for that network group.

650) this.width=650; "Width=" 276 "height=" 435 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/7D/30/ Wkiol1bihmybmmh7aadrqgtni8a303.png "border=" 0 "/>

You can also double-click to manually check out the Copy option.

650) this.width=650; "Width=" 507 "height=" 699 "title=" image "style=" border-top-width:0px;border-right-width:0px; border-bottom-width:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/7D/31/ Wkiom1biheewjby9aaa7bvm3l9i384.png "border=" 0 "/>

The network configuration for this DAG is over.

This article is from the "June Ma Run Space" blog, be sure to keep this source http://horse87.blog.51cto.com/2633686/1749819

Exchange Server 2016 standalone deployment/coexistence Deployment (v)--Configuring Dags (bottom)