Exchange 2010 (ii) MBX DAG deployment

Exchange ( two ) MBX DAG Deployment

The schema is as follows

Master domain control:DCS-01 192.168.2.20

Secondary domain control:DCS-02 192.168.2.21

Certificate Server:CER-01 192.168.2.31

Client Access server 01:cas-01 192.168.2.23 casarray:

Client Access server 02:cas-02 192.168.2.24

Mailbox Transport server :HUB-01 192.168.2.25 NLB:

Mailbox Transport server :HUB-02 192.168.2.26

Mailbox Server :MBX-01 192.168.2.28 DAG:

Mailbox Server :MBX-02 192.168.2.29

The Exchange mailbox database stores all of the users ' messages, so high availability of the mailbox databases in the enterprise is the most important task for administrators. Exchange2007 enables the database to be highly available with LCR,CCR, and CSR, typically CCR(Continuous replication cluster), Exchange2010 is a database availability group (dbAvailable Groups, referred to as a DAG). Dag implements fault tolerance at the message database level, two MBX roles Deploy dags, and the databases on the second platform automatically keep the database synchronized. Deploying A DAG does not require a professional storage device.

Deployment The DAG generally has to pay attention to several

• if when a mailbox server in a DAG group is odd, for example 3 or 5 , no witness is required (the witness is equivalent to a referee)

• of two nodes a DAG requires a witness server (the witness must be in the same forest, a HUB or DC is generally available)

• Same hardware, two NIC

• Disk letter and space are consistent ()

first, the deployment Dag

1. Create a database availability group

1.1 for MBX-01,to add a second network card, for the heartbeat, network card in the same mode network segment can be

650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M00/7A/DE/wKiom1bAhrThXukFAAFm-UynoA8766.jpg "title=" 1.jpg " alt= "Wkiom1bahrthxukfaafm-uynoa8766.jpg"/>

1.2 New Database availability group, such as fill in, the witness server is filled with the FQDN of the DC, the witness directory to fill in random

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7A/DD/wKioL1bAhzujWlQ3AALbQq7rPWI008.jpg "title=" 1.1. JPG "width=" 730 "height=" 459 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:730PX;HEIGHT:459PX; "alt=" Wkiol1bahzujwlq3aalbqq7rpwi008.jpg "/>

Create complete

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M01/7A/DD/wKioL1bAh1KzCOY-AACbt9XhzpU501.jpg "title=" 1.2. JPG "alt=" wkiol1bah1kzcoy-aacbt9xhzpu501.jpg "/>

(1) If you are prompted with errors when creating

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M02/7A/DD/wKioL1bAh3DQuC01AAC38GBY3nA018.jpg "title=" 1.3. JPG "alt=" wkiol1bah3dquc01aac38gby3na018.jpg "/>

(2) need to set the appropriate permissions in advance as shown in Figure 2

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M00/7A/DD/wKioL1bAh4Tyqf2-AALPpQi7z8o047.jpg "title=" 1.4. JPG "width=" 730 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:730px;height:440px; "alt=" Wkiol1bah4tyqf2-aalppqi7z8o047.jpg "/>

2. Add a node server

2.1 Open Organization configuration-mailbox-database Availability Group, right-click the database availability Group

650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M01/7A/DD/wKioL1bAh9SgXsQEAAE1KqzZfg0829.jpg "title=" 1.5. JPG "alt=" wkiol1bah9sgxsqeaae1kqzzfg0829.jpg "/>

2.2 Click Add to add the MBX member server to the Manage Database Availability Group Members dialog box

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/7A/DE/wKiom1bAh4yiu0URAAGTQCA6Oxk340.jpg "title=" 2.jpg " alt= "Wkiom1bah4yiu0uraagtqca6oxk340.jpg"/>

Create complete

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/7A/DD/wKioL1bAh_7zdRc0AAG6gjSPZyU973.jpg "title=" 3.jpg " alt= "Wkiol1bah_7zdrc0aag6gjspzyu973.jpg"/>

2.3 Configure failover , open failover Cluster Manager, configure the clusterIP address

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M02/7A/DE/wKiom1bAh7jyVFgNAAOH1SEzN0A144.jpg "title=" 5.jpg " Width= "730" height= "575" border= "0" hspace= "0" vspace= "0" style= "width:730px;height:575px;" alt= " Wkiom1bah7jyvfgnaaoh1sezn0a144.jpg "/>

2.4 Heartbeat Network --- Cluster Network 1 , the following settings

650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M02/7A/DD/wKioL1bAiEeQ9II-AAJZ8rhJc-k029.jpg "title=" 9.jpg " Width= "730" height= "518" border= "0" hspace= "0" vspace= "0" style= "width:730px;height:518px;" alt= " Wkiol1baieeq9ii-aajz8rhjc-k029.jpg "/>

3. Configuring Database Replication

3.1 Adding a database copy

650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M00/7A/DE/wKiom1bAiAfhA5fpAALCpXozgnQ772.jpg "title=" 6.jpg " Width= "730" height= "427" border= "0" hspace= "0" vspace= "0" style= "WIDTH:730PX;HEIGHT:427PX;" alt= " Wkiom1baiafha5fpaalcpxozgnq772.jpg "/>

3.2 Select the destination server for the mailbox database copy

650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M01/7A/DD/wKioL1bAiI7QS1Y5AAFjMuhTwwQ084.jpg "title=" 7.jpg " alt= "Wkiol1baii7qs1y5aafjmuhtwwq084.jpg"/>

3.3 complete, you can see the current MBX-01 The server is in the "Mount" state, MBX-02 to "normal" status

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M02/7A/DD/wKioL1bAiK3T0ejqAAKth9OtWvQ483.jpg "title=" 8.jpg " Width= "730" height= "420" border= "0" hspace= "0" vspace= "0" style= "width:730px;height:420px;" alt= " Wkiol1baik3t0ejqaakth9otwvq483.jpg "/>

3.4mbx-02 also copy on on the Database01 the database files and log files

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M00/7A/DD/wKioL1bAiNWh_lMqAAEGUhVRtwQ651.jpg "title=" 10.jpg "alt=" Wkiol1bainwh_lmqaaeguhvrtwq651.jpg "/>

3.5 one node server down test, if you see, shut down one and one can provide data services

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/7A/DD/wKioL1bAiPDgkhLZAACNZ71agBw116.jpg "title=" 11.jpg "alt=" Wkiol1baipdgkhlzaacnz71agbw116.jpg "/>

This article is from the "Zhao Dongwei Learning record" blog, so be sure to keep this source http://zhaodongwei.blog.51cto.com/4233742/1741981

Exchange 2010 (ii) MBX DAG deployment