Today is a simple way to say how highly available in the Exchange 2016 deployment dag.
Demo Environment:
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "alt=" image "src=" http://s3.51cto.com/ Wyfs02/m01/71/89/wkiom1xtm72btii_aacg7lgdmz0795.jpg "height=" 283 "border=" 0 "width=" 396 "/>
1dc+2exchange 2016
Deploying a DC Step ignores
Deploying Exchange 2016, Reference link: http://gshao.blog.51cto.com/3512873/1685238
Let's start with the deployment of the exchange. Dag, which is actually the same as the DAG.
1. Add the Exchange Trusted subsystem to the Administrators group because this is the DC server as the witness server;
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/71/89/wkiom1xtm76c0c9iaakv80kxovy822.jpg "height=" 508 "border=" 0 "width=" 718 "/>
2. Login to EAC, server-database availability group, new 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;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/71/86/wkiol1xtncuyf16uaag3xpwfmrk581.jpg "height=" 570 "border=" 0 "/>
Add: It is not recommended to create a new witness folder directory for everyone (unsafe for the enterprise), and if not, the DAG will make the corresponding witness directory on its own. We can simply take a look at what the system creates a witness directory for.
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;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/71/86/wkiol1xtncuik5dlaadnttiurmq593.jpg "height=" 265 "border=" 0 "/>650) this.width=650 ; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0px;padding-top:0px; padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/ 71/86/wkiol1xtncyakzs4aaf8vs7ormi069.jpg "height=" 425 "border=" 0 "/>650) this.width=650;" title= "image" style= " border-top:0px;border-right:0px;background-image:none;border-bottom:0px;padding-top:0px;padding-left:0px; border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/71/86/ Wkiol1xtncydkhvvaageypy2rvu262.jpg "height=" border= "0"/>
Create a good DAG
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/71/86/wkiol1xtncybazegaacuesnr6rk137.jpg "height=" 198 "border=" 0 "width=" 649 "/>
3. Add a member server to the DAG database availability Group;
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/71/86/wkiol1xtnc2rnnwlaafjdianwpq109.jpg "height=" 383 "border=" 0 "width=" 540 "/>650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/71/86/wkiol1xtnc3ismxlaafr2qtwvgi781.jpg "height=" 505 "border=" 0 "width=" 547 "/>
4. Modify the DAG production network and Replication network
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/71/86/wkiol1xtnc7c1akoaaft4famcuk434.jpg "height=" 501 "border=" 0 "width=" 753 "/>
5. Add replication network replicationnetwork;
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;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/71/89/wkiom1xtm8otfb8qaafqpymukh4629.jpg "height=" 452 "border=" 0 "/>
6. Configure the database copy;
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;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/71/89/wkiom1xtm8oxmingaacf-dw5lnm072.jpg "height=" 167 "border=" 0 "/>
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;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/71/89/wkiom1xtm8os9q6baaeh7rmxomu377.jpg "height=" 428 "border=" 0 "/>650) this.width=650 ; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0px;padding-top:0px; padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/ 71/89/wkiom1xtm8tcgjfmaafw0zjtxsm584.jpg "height=" 444 "border=" 0 "/>
Previously mentioned in the Forum the functionality of the new Exchange 2016 architecture (http://blogs.technet.com/b/exchange/archive/2015/05/05/ Exchange-server-2016-architecture.aspx), theDag section is improved to:
1) DAG IP can not be set, of course, Microsoft is recommended to set the
2) By default, replay delay management is initiated. (The Exchange DAG has the replaylagmanagerenabled parameter to disable automatic reduction of log files for deferred database copies, typically in a cross-site Dag, which is prohibited by default)
3) Lagged database copy fades can delay based on disk latency, thus ensuring that active users are unaffected.
4) database failover time is reduced by 33% compared to Exchange 2013
650) this.width=650; "title=" image "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/71/8A/ Wkiom1xtm8sdderbaahttlak7be404.jpg "height=" border= "0"/>
Let's look at the EMS to see if the properties of the DAG group are replaylagmanagerenabled true
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;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/71/86/wkiol1xtndghotrpaacvwdb-czu722.jpg "height=" 104 "border=" 0 "/>
I was looking at the expression of the situation:
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;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/71/86/wkiol1xtndkqkba2aadeccjkpb8944.jpg "height=" 273 "border=" 0 "/>
Today is Jiangzi, I draw the circle to go ...
This article from "Gs_hao" blog, declined reprint!
Exchange 2016 's exchange DAG is highly available