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

According to the plan, the witness server in the case uses a special virtual machine, and the virtual machine joins MC.com in advance. Therefore, you first need to grant the appropriate permissions to the domain controller so that DAG can be deployed properly. It is recommended that you follow the following procedure.

Witness authorizes access to create DAG add Node Server to DAG Test Database copy

I. Witness server authorization

In practical application, the location where the witness server may be deployed is as follows.

Exchange Server server. Note: the witness cannot be deployed in a mailbox server that participates in DAG. Other servers, such as domain control servers, file servers that join the domain, and so on.

The roles in the case are as follows.

192.168.188.221 (AD01) 192.168.188.222 (AD02) 192.168.188.223 (Ex01) 192.168.188.224 (Ex02) 192.168.188.225 (Ex03) 192.168.188.226 (witness) 192.168.188.227 (DAG)

In this case, the witness uses a dedicated machine, so the "Exchange Trusted Subsystem" security group is added to the local administrators group before deploying DAG to ensure that the witness directory is automatically created during the deployment of DAG.

The first step is to log in to the AD server as an administrator and add Exchange Trusted Subsystem to the local administrators group, and Exchange Trusted Subsystem to the local administrators group at the witness. If you do not authorize, an access denied error will occur when creating the witness directory.

Create the target computer and disable it

The first step is to log in to the domain controller, open "Active Directory users and computers, and create a computer account with the same name as the DAG group. The parameters are as follows:"

Step 2, add the DAG computer account to the Exchange Trusted Subsystem group, as shown in the figure

The third step is to enable the advanced features options for Active Directory users and computers, open the DAG computer account Properties dialog box, switch to the Security tab, add all DAG member servers to the safe list, and give full control.

The fourth step is to disable computer objects.

Third, create A record

Open the DNS console and create an "A" record with the same name in DAG. The completed A record is as follows.

IV. Configure and deploy DAG

In an Exchange Server2019 environment, DAG is deployed through the Exchange Management Center. The access method is as follows: http:// Mailbox server / ecp

1. Create a DAG

The first step is to open the browser, log in to the Exchange Management Center, select the "Server" option in the left list, and select the database availability group. No DAG group is created by default, as shown in the figure.

Second, click the + button to open the New Database availability Group dialog box. Where:

Database availability group name: sets the name of the DAG, which must ensure the uniqueness of the "Active Directory" witness: sets the location of the witness. In this case, using a server that joined AD, type its full FQDN witness directory: leave it blank, and the witness directory is automatically created during DAG creation. Of course, it can also be specified manually. Witness directory default location "% systemdrive%\ DagFileSareWitnesses\". When individuals test version 2019, the default error will occur when testing. It is recommended to customize the directory and share folders. Database availability group IP address: set the IP address used by DAG. Set the parameters in the "enter IP address" text box as shown in the figure

Click the Save button and start creating the DAG. After creating the DAG, return to the Database availability groups window, the newly created DAG is displayed in the list, and the location of the witness server is shown on the right. As shown in the figure, although DAG was created successfully, it did not add any node servers.

2. Add a node server

After the DAG is created successfully, the Mailbox server is not automatically added, and the Exchange administrator is required to manually add it to complete the task.

First, in the database availability group window, select manage DAG membership, as shown in the figure

The second step is to click the "manage DAG membership" icon to open the "manage Database availability qualifications" dialog box. No node servers have been added by default.

The third step, click the "+" button, open the select server window, select the mailbox server, click the "add" button, and add the selected target server to the text box on the left side of the button, as shown in the figure

Step 4, click the OK button to return to the manage Database availability eligibility dialog box, and add the selected server to the list

Step 5, click Save, and the server will join the DAG group.

When the operation is complete, the failover cluster role is added to each node, the cluster is created, the cluster node is joined, and so on until it is complete.

Step 6, return to the Database availability Group window. As shown in the figure, the list of member servers shows the mailbox servers that have been added. Details are displayed on the right.

Member servers: MCEX01, MCEX02, MCEX03 witness: MCZC01DAG network: MapIDagNetwork

3. Configure the cluster network

When the DAG is created successfully, the application network is used as the cluster network by default. In this case, two sets of networks are deployed: the application network (internal network) and the replication network (heartbeat network), so the administrator is required to configure the replication network.

The first step is to open the Database availability Group, select the created DAG, then select the pen icon on the toolbar, and edit the DAG property, as shown in the figure

The second step, after the command is executed, the "General" option will be turned on by default, as shown in the figure, select the "manually configure data availability group network" option, click the Save button, and complete the DAG property setting.

Step 3, click "New DAG Network" on the toolbar as shown in the figure.

Fourth, after the command is executed, open the "New Database availability Group Network" window and type the network name in the "Database availability Network Group Network name" text box, as shown in the figure

Step 5, in the "Subnet" area, click the "+" button to open the "add Subnet" dialog box. In this case, the planned replication network is 1.1.1.0 to 24. Type the parameters related to the replication network, and set the parameters as shown in the figure.

Step 6, click "Save" to return to the "New Database availability Group Network" window. The new subnet is displayed in the "Subnet" list, as shown in the figure

Step 7, click the Save button to complete the DAG replication network you created. As shown in the picture

Step 8, according to the planned name of the network "ReplicationDAGNetwork", that is, the "heartbeat network". To complete the mailbox database replication function, the application network provides services to the outside world, so it is necessary to disable the replication function of the application network. Click disable replication under MapiDagNetwork under Dag Network, and the warning dialog box appears as shown in the figure, prompting you to disable replication.

Step 9, click the "OK" button, the replication function of the "MapiDagNetwork" network is disabled, as shown in the figure, the replication status is updated from "disable replication" to "enable replication", indicating that the replication function of the current network is disabled.

Step 10, click the "View details" link under the "MapiDagNetwork" network card to display the subnet used by the "MapiDagNetwork" network and the network interface is enabled (UP). Note that the "enable replication" option is unchecked, as shown in the figure

Step 11, click the "View details" link under the "ReplicationDAGNetwork" network to display the subnet used by the "ReplicationDagNetwork" network and the network interface is enabled (UP). Note that the "enable replication" option is selected, as shown in the figure

5. Verify DAG

1. After the DAG is successfully created, in the AD computer "users and computers"

The Computer:DAG machine has been enabled and is marked as follows

2. Verify the witness directory

In the folder directory specified by the witness server, there will be two more files as follows

3. Verify the running status of the cluster service

Open the service console in each mailbox server, there will be Cluster Service, and run automatically

4. Verify the failed cluster failover node console

You can see the health of each node through the failover console. Exchange uses Windows Server2019's failover clustering service to detect the status of DAG node servers. The information is as follows

1) role options

No Exchange applications are deployed in the role options. Exchange failover is done by the DAG function of Exchange and does not require the cluster service of Windows Server2019, so you do not see any Exchange-related roles in this option. As shown in the picture

2) Node option

In the node option, all node servers added in the database availability group are displayed as cluster node servers, and the server status is normal as shown in the figure

3) Storage-> disk options

In the storage options, you cannot see any disk information because no shared storage is used, as shown in the figure

4) Network option

In the network option, each server in the database availability group uses two network cards, one to connect to the application network (192.168.188.0) and one to connect to the service network (heartbeat network 1.1.1.0). The network status of all node servers is running normally. By viewing the summary and network connection, you can view the detailed configuration as shown in the figure.

VI. Database copy testing

1) create a new mailbox database

During the deployment of Exchange Server 2019, a system database is automatically created, which differs from the new mailbox database in that several system mailboxes are built in. Therefore, it is recommended that you use the newly created mailbox database when testing DAG. In this test, you will create the test mailbox database "TestDB01" in the "MCEX01" server

In the first step, open the Exchange Central Administration and select the server option in the list on the left, and select the database option on the right. The list displays all deployed Exchange mailbox databases, as shown in the figure

The second step, click the "+" button, open the "New Database" window, set the mailbox database name to "TestDB01" and select the "load this database" option by default. As shown in the picture

Third, click the browse button on the right side of "Server" to open the Select Server window, select the target server, and create a mailbox database in the target server. In the case, select the "MCEX01" server, as shown in the figure.

Step 4, click the OK button to return to the "New Database" window, as shown in the figure. After selecting the server, the database file and log file named after the mailbox database are automatically created in the default folder.

Step 5, click the Save button to display the warning dialog box below, indicating that the Microsoft Exchange Information Storage service needs to be restarted.

Step 6, click the OK button to successfully create a test database named "TestDB01", as shown in the figure

Step 7, restart the Microsoft Exchange information storage service as prompted

2) deploy mailbox database copy

The first step is to select the newly created test database "TestDB01" in the database list, and then click "…" on the toolbar. Icon, click "add database copy" in the pop-up list as shown in the figure

Second, after the command is executed, open the "add Mailbox database copy" window, as shown in the figure

Third, click the "Browse" button to open the "Select Server" window. Once again, we choose one at random, as shown in the figure.

Step 4, after selecting the target server, click the OK button to return to the "add Mailbox database copy" window. The selected server is added to the text box under "specify Mailbox Server", as shown in the figure.

Step 5, click the Save button to start creating a copy of the database, which goes through some three processes

Set the seed. Synchronize mailbox databases. Create a content index.

After the above three procedures are completed, the following dialog box will be displayed. Click the close button to complete the copy creation process. If there are no errors, the DAG is created successfully.

VII. Wrong solution

1. Access denied

In the process of deploying DAG, the solution to the "access denied" error is as follows: grant "Exchange Trusted Subsystem" permission to the server in the DAG server role and grant full control rights.

2. The cluster network name resource cannot register one or more associated DNS names because access is denied while updating the secure DNS zone. Cluster network name: cluster name

DNS area: "MC.com"

Be sure to grant the cluster name object (CNO) permission to the secure DNS zone.

To solve this problem, you need to delete the original DAG-related A record in DNS resolution, then create a new A record again, and check to allow all authenticated users to update the DNS record with the same owner name.

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.