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

Catalogue

1 Software Resources 2

2 install Exchange 2010 SP3 2

3 install Exchange 2010 SP3 RU26 8

3.1 condition preparation 8

3.2 detailed step instructions 8

3.2.1 download and run Microsoft Visual C++ 2013 Redistributable (x64) 8 directly

3.2.2 install Exchange 2010 SP3 RU26 8

4 build DAG environment 10

4.1 preparation conditions 10

4.2 Environmental preparation 10

4.2.1 Network Card Settings 10

4.3 create database availability group 10

4.3.1 step instructions: 10

4.3.2 create a database replica 16

Deployment of Exchange 2010 SP3& upgrade to RU26& deployment DAG environment step instructions

1 Software resources

 operating system: Windows Server 2012 R2

 email application: Exchange Server 2010 SP3

 FilterPack64bit-2010

 Exchange Server 2010 SP3 RU26 Patch

 Microsoft Visual C++ 2013 Redistributable (x64)

2 install Exchange 2010 SP3

1. According to the official deployment documentation, FilterPack64bit-2010 is required to install Exchange 2010 SP3.

2. Open FilterPack64bit-2010

3. When Exchange2010 server is installed, it needs to be supported by corresponding operating system components, which are roles and functions in 2012 R2. It is best to use Powershell to install the components required for Exchange2010, which can be easily done in a few sentences. Installing different Exchange2010 roles requires different Powershell statements. For more information, please see

Https://technet.microsoft.com/zh-cn/library/bb691354(v=exchg.141).aspx

Command: Import-Module ServerManager

4. Install the necessary operating system components using Add-WindowsFeature cmdlet

(1) since Windows Server 2012R2 does not have built-in functions such as NET, you need to mount the system installation image on the server (such as disk D) and add-source D:\ sources\ sxs to the command.

(2) run the following command as an administrator in powershell to install the Hub Transport and Mailbox server roles on the server.

Add-WindowsFeature NET-Framework-Features,RSAT-Clustering,WAS-Process-Model,Web-Basic-Auth,Web-Lgcy-Mgmt-Console,Web-Metabase,Web-Mgmt-Console,Web-Net-Ext,Web-Server,Web-Windows-Auth-Restart-source D:\ sources\ sxs

The server needs to be restarted after installation is complete.

5. After the above is ready, you can run the Exchange2010 (this time Exchange2010 SP3) installation package

You can find that the previous step is grayed out, indicating that it has been completed. Click step 4 to continue:

You can choose the type according to your own situation: (this time, select the Mailbox server role and Hub Transport role)

You can enter your own company name for the Exchange organization name:

If the client has 2003, you can choose, otherwise choose No:

The following allows you to configure the address of the client when accessing on Internet (the user is not in the company and wants to use the web mailbox outside), as follows:

Check the previous prerequisites:

After the installation is complete, install another server in the same way.

3 install Exchange 2010 SP3 RU26

3.1 conditional preparation

 installs Microsoft Visual C++ 2013 Redistributable (x64) as an administrator

 adjusts the system area to: UK (USA)

3.2 detailed step instructions

3.2.1 download and run Microsoft Visual C++ 2013 Redistributable (x64) directly

3.2.2 install Exchange 2010 SP3 RU26

1) adjust the current system area, in the control panel-- "clock, region and language"-- Select "region"-- Select "Management"

2) in the "languages of non-Unicode programs" area, select "change system locale"

3) in the "current system locale" list, select "UK (USA)", and then select "OK"

4) run the RU26 installation package as an administrator, and after the installation is complete, you can return the system area to the original default settings.

4. Build DAG environment.

4.1 preparation conditions

 has at least two MBX servers, and both servers have dual network cards. One network card is used to provide client access, and the other provides database replication.

 creates a high availability group for database servers-DAG failover cluster

 two MBX servers both need corresponding database copies-data synchronization

4.2 Environmental preparation

4.2.1 Network Card Settings

1) in the environment, the MBX server each has two NICs, one is the LAN Nic, and the other DAG Nic is used synchronously as a database high availability:

2) the network segment of LAN network card is 192.168.100.0and24DAG network card: 192.168.200.0and24.

4.3 create a database availability group

4.3.1 step instructions:

1) Open the Exchange console-Organization configuration-Mailbox-Database Management: view the current database containing two MBX servers

2) create a database high availability group:

3) name of the custom group, such as DAG

Configure witness server: it can be an Exchange server or a non-Exchange server. If it is an Exchange server (such as a front-end server), you can "create" it directly without any settings:

4) Click finish:

5) after completion, you can see the witness server and the directory:

6) right-click the "Properties" of DAG, and set the IP address of DAG. The IP address is the IP of the same network segment as Cluster:

!

7) to add group members, click "manage database availability group members" in the lower right corner:

8) add two MBX servers:

9) Click finish:

10) you can see that the member server has been displayed:

11) configure the DAG network

Right-click the attribute to change the name, such as MAPI, the subnet remains default, and replication cancellation is enabled. This ensures that the 100.0 IP address range only helps us to make a client access, and the synchronization of the database replica will not be synchronized through the 100.0 IP address range:

4.3.2 create a copy of the database

1) Select the database of MBS02 and create a copy:

2) specify the name of the server and select the MBS01 server:

Activation preference number: the database availability group supports up to 16 database replicas. If the database of the group fails, which copy of the remaining copy will serve the client as the active state and be decided by this number; the numbering rule: the second server added is numbered 2, and the third server is numbered 3.

3) Click finish, and the database copy of MBS02 is created on the MBS01 server:

4) the status appears normal after synchronization:

Note: the client accesses normally and accesses the database with MBS02 and active status of True. When the database is changed, it will be copied to the replica on MBS01, thus keeping the two MBX servers synchronized.

Case analysis

1) if you want to install a patch for MBS01 first, you can stop the replication of the database copy and choose to shelve:

2) after restarting the MBS01 server, you can resume replication

Next, update the server MBS02, which is an active True. First, you need to switch the active database to MBS01, select the MBS01 copy, and click activate:

3) Select "Lossless":

4) you can see that the copy of the database on MBS01 becomes active:

5) you can install a patch and restart the MBS02 server at this time, and then switch back

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.