High-availability deployment of the Exchange Server for Dags (vi)-DAG configuration (top)

After completing the other configuration of the mail server mentioned in the previous article, in theory, after creating a new mailbox user, you can already start sending and receiving messages normally. But our focus in this series is on the highly available deployments of dags, so let's take a closer look at the configuration steps of the DAG.

22. Configuring the witness server

First, join the Exchange Trusted Subsystem user group to the Administrators group to ensure access to the underlying features of the witness server

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/5B/5B/wKioL1UHkZjC9gktAAKG3x3pUq0072.jpg "height=" 441 "/>

Then create a DAG's host a record, assigning an IP address of the same network segment

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/5B/61/wKiom1UHkHLzrKIQAAJYViSig20162.jpg "height=" 382 "/>

Then create a computer named Dag in AD and disable

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/5B/61/wKiom1UHkHOTbFmXAAFMU1P7tF8200.jpg "height=" 384 "/>

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/5b/61/wkiom1uhkhoj0csqaae_xw3ajfm917.jpg "height="/>

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/5B/5B/wKioL1UHkZvhKUetAAHtNURHTh8893.jpg "height=" 479 "/>

Advanced features for using AD tools

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/5B/5B/wKioL1UHkZzQQwC0AAHXPvfqR_s594.jpg "height=" 484 "/>

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/5B/5B/wKioL1UHkZ3SnXyWAAIoliKfuf0308.jpg "height=" 465 "/>

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/5B/61/wKiom1UHkHeRmqc6AAKRT5_0pDk625.jpg "height=" 484 "/>

In the security options for the DAG computer, add two back-end databases MBX the server and give Full Control permissions

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/5B/61/wKiom1UHkHijTP4GAAHDpwSNaiU963.jpg "height=" 484 "/>

23. Create a DAG availability Group

In the ECP console, select Servers-Data availability groups-add to create a DAG group, enter the group name and the witness server, and the IP address in the a record on the previous DNS

BTW: From Microsoft best practices, but also to prevent single point of failure, here we will witness the server selected as domain control

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/5B/61/wKiom1UHkHnTmYL9AAGgr29fZxI074.jpg "height=" 471 "/>

After creating the DAG Group, double-click to add two back-end MBX servers as member servers for the database availability Group

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/5B/61/wKiom1UHkHrj9kGbAAGb_amvpB4079.jpg "height=" 444 "/>

Click Save to complete the add

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/5B/61/wKiom1UHkHqBLgHrAAGHh_ujoIk880.jpg "height=" 442 "/>

24. Create a DAG network

Double click Create a DAG availability group, tick the "Manually Configure Database Availability Group Network" below

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/5B/61/wKiom1UHkHuCuOM2AAGTknOnU90023.jpg "height=" 457 "/>

Click "View Details" on the DAG Network

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/5B/61/wKiom1UHkHyRQ42cAAFKl64X7bg896.jpg "height=" 395 "/>

Into the detailed list of DAG networks, we can see that there are two sub-networks, one is the production segment (CAS and MBX communication network segment), the other is a private segment (this segment is only used as a DAG exclusive replication segment), select the private segment click "Delete"

BTW: From this figure we can determine that two back-end MBX server must have two network cards, one is the production business network card, one is the DAG replication network card, need to be allocated to two different network segments, and two network segments within each other.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/5B/61/wKiom1UHkH3geTjtAAHauNhSxrY468.jpg "height=" 480 "/>

Then click "New DAG Network"

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/5B/61/wKiom1UHkH3xaSicAAEdQ412Ca0695.jpg "height=" 385 "/>

Then write to the database Availability Group Network name, in order to differentiate with production network segment, can take a better distinguished name, I use here is to copy the name of the network, and then add the subnet we just deleted here

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/5B/61/wKiom1UHkH6ybiLHAADCR0OiR1k468.jpg "height=" 392 "/>

At this point, we can see that there are two networks in the DAG Network, one is the default, and the other is our new one. Click "Disable Replication" on the default network

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/5B/61/wKiom1UHkH_BviEqAAEdXshwOQI526.jpg "height=" 379 "/>

We can logically understand that the first default network is only used as a front-end CAs and client for data communication, but only our new replication network is actually used to do the database copy bidirectional synchronous replication data.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;margin:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/5B/61/wKiom1UHkH-B8tspAAEiazdQU8Q874.jpg "height=" 385 "/>

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

High-availability deployment of the Exchange Server for Dags (vi)-DAG configuration (top)