Shulou(Shulou.com)05/31 Report--

How to understand DAG high availability of Exchange Server 2010? I believe many inexperienced people don't know what to do about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

We introduced the building of the Exchange Server 2010 server earlier, as well as how to request the appropriate certificate for Exchange. In other words, we can now use the built Exchange server to send and receive email. So, if we build only one Mail server in the company, it can not guarantee our high availability and high reliability. For example, in Exchange 2007, we can use CCR+SCR to solve the high availability and high reliability of the company's Mail server. Then today in the Exchange Server 2010 version, I will introduce how to use DAG (database availability group) technology to solve the high availability and high reliability of Mail server. Well, then we will prove the construction of DAG technology through experiments.

First of all, let's introduce our topology.

DC, EX01 and EX02 have been built in advance, and EX01 and EX02 have been added to the domain as member computers. We need to ensure that the membership of EXC01 and EX02 are the same, so that there will be no problems in the whole experimental environment.

In fact, the DAG technology of the Mail server is to establish the cluster technology, so in DAG, we also have a requirement, that is, in the environment of even nodes, we need to create an arbitration folder, odd nodes do not need to create an arbitration, generally speaking, we create this arbitration on the HUB server, but note that we cannot be together with the mailbox server role. So in our environment, we can only establish arbitration on the DC server. Also note here that in our environment, I created the witness (arbitration) folder on DC, so if the witness disk is created in a non-Exchange environment, we also need to

Create a folder on the C disk of DC and share it. The adminsitrators group has full control in the sharing permission, and the NTFS permission is also under full control.

OK, we have created the arbitration documents. So what we need to do next is to create a DAG group on EX01. We can use the powershell command to create a DAG group, as follows

Open the powershell console and enter new-databaseavailabilitygroup-name DAG1-witnessserver DC01-witnessdirectory c:\ dag1-databaseavailabilitygroupipaddresses 10.1.1.100

10.1.1.100 We can understand that it is the cluster IP. After the creation is completed, we can check it in EMC.

The scaffolding will find that there is no member server in the created DAG group, so at this time, we need to add the DAG members manually.

Just select two servers to add in. Since we did not add the "failover cluster" feature in the server manager, it will be added automatically in this step, so it will take some time to add.

After the addition is successful, let's check it out.

The main idea of DAG is the high availability of databases, which is realized by using the technology of continuous database replication, which is also first referenced in Exchange2007. Therefore, you should have your own DB1 and EX02 DB2 on the EX01 server, and your own DB2 and EX01 DB1 on the EX02. Therefore, this environment mounts two disks, E and F, for each MailBox server.

Then move the DB1 database to disk E on EX01 and rename it

Similarly, move the DB2 database to disk F on EX02 and rename it

OK, now that we have moved the DB1 of EX01 to the local E disk and the DB2 of EX02 to the local F disk, then even so, there is no reliability and high availability. We need to have DB1 on EX01 and DB1 and DB2 on DB2; on EX02. Therefore, we need to create database replicas on EX01 and EX02 respectively to enhance the high availability of MailBox

Also add a copy of the mailbox database for EX02, and then we see that DB1 is mounted on EX01, while DB2 is normal on EX01, that is, a copy of EX01; DB2 is mounted on EX02, and DB1 is normal on EX02, that is, a copy of EX02. When the DB2 is offline, the DB1 on the EX01 will be loaded and accessed by users in the DB2.

OK, the future DAG configuration is over. Next, let's verify it.

In EX01, we create an account wangwu which belongs to the DB2 mailbox database and uses DC as the client to access it.

Now let's manually take EX02 offline and visit it again.

Prompt us to wait until 10 seconds later (the normal waiting time is about 30 seconds). Okay, visit again.

We can also check the status.

Ok, we succeeded in the experiment!

After reading the above, have you mastered how to understand DAG high availability in Exchange Server 2010? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.