Shulou(Shulou.com)06/02 Report--

Compared with the previous 2010, the new version of the new generation of mail system has abandoned the original EMC management interface and replaced it with EAC (Management Control Center).

After completing the deployment of all mailbox roles and the deployment of NLB, we then proceed to the high-availability configuration of DAG:

Database availability groups (DAG) are the basic components of the high availability and site recovery framework built into Microsoft Exchange Server 2013. DAG is a set of Mailbox servers (up to 16 Mailbox servers) that hosts a set of databases that provide the ability to automate database-level recovery from failures that affect a single server or database.

DAG configuration steps:

1. Enter: https://mail.lt.com.cn/ecp in the browser. Log in to the ECP management interface, click-Server-- Click Database availability Group-Click New: create a database availability group, enter the DAG name and witness server, which is generally configured on CAS, or on your other server such as domain controller: in this example, DC is used as witness server. If the CAS server is shut down, the witness server will not be affected:

two。 From the figure above, we can see that since the domain controller is not in the exchnge trusted subsystem, we join Exchange Trusted Subsystem to the Administrators group on the domain:

3. The witness directory can be left empty, so DAG will automatically create the witness directory in the corresponding server. You can also specify it yourself, because my witness directory is above the primary domain, so a new DAG directory is created on disk C in the primary domain 2003-AD.

Add cluster IP, add cluster member server-save

4. The following is to configure the replication network, select DAG, edit, and check manually configure the database availability group network. Save.

5.

Open the following figure in the DAG network to view the details. Next step we are to continue to configure the network, take a closer look (see figure 1), no, why there is only MAPI network, no Replication network, EAC control center seems to need to be improved, fortunately, I have done several such projects, know the cause of the failure, return to the previous step, manually configure database availability group network uncheck, save, re-select manually configure database availability network again Surprise appeared, everyone look at figure 2, ha ha, the replication network has come out.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.