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

precondition

MB IP

Heart network

192.168.1.15

192.168.100.2

192.168.1.16

192.168.100.3

Dag Cluster Virtual ip

192.168.1.30

DAG network card configuration

The purpose of configuring DAG is to enhance the high availability of the mail server and to avoid the mail system users being unable to access the mailbox after a Mailbox server is damaged.

When configuring DAG, it is better for the Mailbox server to have two network cards, one for production environment and the other for replication between DAG.

Before creating a DAG, first make sure that all servers in the Exchange belong to the Exchange Trusted Subsystem group

The DAG network card does not need to be configured with DNS and gateway. Each machine needs a DAG network card

Network card connection settin

Witness server configuration

It is generally recommended that you use the CAS server as the DAG witness, and when you choose a non-member of the Exchange server role (except the Edge Transport server) as the witness, you need to add the group "Exchange Trusted Subsystem" to the local administrators group of the witness. Otherwise, it will lead to an error in creating DAG. This article chooses DC as the witness server.

BEN

Create DAG

Open any exchange server, open the EMC Management console-Organization configuration-mailbox, and switch from the middle pane to the Database availability groups tab. Right-click "New Database availability Group" in the space, and the interface shown in the following figure appears:

Enter the name of the DAG here, specify the name of the DAG, and the witness server to witness the directory

(note: the witness directory witness does not need to be created manually. DAG will automatically create and share after adding members.)

The warning can be ignored, because in the first step, we have joined the Exchange trusted subsystem group to the local administrators group of the domain controller. Click "finish", and the DAG will be created successfully.

In the completion interface, you can see the corresponding command line. Next, we need to set the cluster IP address of DAG by right-clicking "Properties" on the newly created DAG name-switch to the "IP address" tab and add it. As shown in the following figure:

To add the database availability group IP address, click "OK", but there are no members in our DAG group yet, so we need to continue to add members to the DAG, that is, to add the exchange mBX server to the availability group. Right-click on the newly created DAG name "manage database availability group membership", and then add ex01 and ex02. As shown in the following figure:

When you click "manage", you need to wait a moment, because the system also needs to install Windows's failover clustering service on the member machine while joining the member.

Here is how to add database high availability group members using commands in Exchange Management Shell

Add-DatabaseAvailabilityGroupServer-Identity cqdag-MailboxServer cqexdag01

Add-DatabaseAvailabilityGroupServer-Identity cqdag-MailboxServer cqexdag02

After adding the DAG member, we go to disk c of the domain controller to verify that the witness directory is automatically created and shared

Next, looking at the resources in the failover cluster, we can open the failover cluster administrator on any exchange server, and you can see from the figure below that the cluster name is the DAG01.lsx.com that we specified in the DAG deployment. Both nodes in the cluster are in a normal state.

DNS records are automatically created

In our initial plan, the dag network card is used as a data replication network card, which is located in the network segment of the replication network 192.168.100.0, so now the MAPI network, that is, 192.168.1.0, can also be used for replication. Here we disable the replication of the MAPI network.

Let's add a copy of the mailbox database, which is actually creating a backup on another mailbox server, but first let's create a new database. The default database is not used here.

Switch to the Database Management tab, right-click in the space and select "New Mailbox Database"

Specify the database name to be the server that hosts it

Specify the database file path and the folder path where the logs are stored

Click "finish", and a mailbox database mb01 is created.

Create and load mailbox database using command in Exchange Management Shell

Create and load the database on another exchange server with the command

New-MailboxDatabase-Server ex02-Name mb02-EdbFilePath c:\ mailbox\ mb02\ mb02.edb-LogFolderPath c:\ mailbox\ mb02log

Mount the database

Mount-Database-Identity mb02

As shown in the following figure, the mailbox database is created

Create a copy of the mailbox database

Right-click on mb01 and select "add Mailbox Database copy"

Specify the server where the copy of the database is stored. Select ex02 here.

Click "add" to create successfully

Add a copy of mailbox database by command in Exchange Management Shell

Create a copy of the MB02 database using Exchange Management Shell

Add-MailboxDatabaseCopy-Identity MB02-MailboxServer EX01-ActivationPreference 2

Now we can see that the mailbox databases MB01 and MB02 have copies on both mailbox servers.

Test DAG

Pause the EX02 server

The following figure shows that the database has been switched to the EX01 copy

Can send and receive normally

View the header to show that it is sent and received by the EX01 server

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.