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

SFB project experience-51-2, 000 people in a listed company Exchange 2013 upgrade 2016 high-availability injury 01 (write project notes with illness)

Problem description:

2000 people enterprises use Exchange 2013 mail server standard edition, n years!

1) question 1:

Standard Edition supports only 5 mailbox databases.

2) question 2:

A mailbox database user is too many, mailbox capacity is too large 500GB-1TB, easy to often die.

SFB project experience-49-it takes 5 days to repair the mailbox database of 2000 people in a listed enterprise (May Day contribution)

Https://blog.51cto.com/dynamic/2109395

3) question 3:

The local hard disk uses a virtual machine to map the hard disk to a network drive to store the database.

4) question 4:

Local memory 24GB, generally run to 22GB, any operation you get stuck, as long as you more than 2 times, die to show you.

5) question 5:

Certificate names pile after pile, it is really thousands of degrees to find it, silently looking back only in a pile of garbage.

6) question 6:

There are two Exchange 2013 in the environment, one of which is out of date.

Solution:

Upgrade!

Upgrade to Exchange 2013 High availability, before 2, after 2, at least 4 mail servers.

Upgrade to Exchange 2016 High availability, 2 Mailbox server roles, at least 2 mail servers.

Submit the proposal, veto!

A WeCom accident, affecting about 2000 people, roughly affected about 3 days, and most people lost their contacts and chat records.

Decided to upgrade to Exchange 2016 High availability.

Upgrade planning (rough planning):

1) using co-existing upgrades to ensure a smooth transition without affecting the normal use of Exchange 2013.

2) Anti-spam is old, use the current barracuda to prevent spam.

3) the operating system adopts Windows 2012 R2, which is universal and easy to use. (wise choice)

4) Exchange 2016 uses Exchange 2016 CU10. (wise choice)

5) using DNS round robin, using 2 public network IP,2 bar A to record mail.contoso.com,2 bar public network A record Autodiscover.contoso.com.

6) use 2 64GB physical servers, 6 4TB hard drives, RAID10.

7) each physical server has 2 gigabit NICs, one for LAN,1 and one for Private.

8) the mail server database is designed by DAG, with one master and one copy, and one virtual machine is prepared as the witness server.

9) skip...

Escalation pain:

1) learn to use Windows 2012 R2 AD + 2 Exchange 2013 RTM in your environment.

2) learn to upgrade to Exchange 2016 CU10, at least Exchange 2013 CU10. This time, use Exchange 2013 RTM to upgrade to Exchange 2013 CU 21 and then upgrade to Exchange 2016 CU10.

3) simulated test environment

a. With 5 Windows 2012 R2 virtual machines

b. Among them, 2 domain controllers are 011-DC01012-DC02, and 011-DC01 is also a certificate authority, which provides certificate issuance.

c. One of the mail servers is 021-mail01, with Exchange 2013 RTM installed and upgraded to Exchange 2013 CU21.

d. Create a new test account, configure Outlook, and test whether it is normal to send and receive email.

e. Two of the mail servers are 031-mail01 with Exchange 2016 CU10 installed.

f. Create a new test account, configure Outlook, and test whether it is normal to send and receive email.

g. Migrate the test account to test whether it is normal to send and receive email.

h. Switch the mail record to Exchange 2016 CU10.

i. Test whether the account can use Outlook properly and whether it can send and receive email normally.

j. Power off the Exchange 2013 CU21.

k. Test whether the account can use Outlook properly and whether it can send and receive email normally.

4) upgrade of normal environment

A. Hang 1:

The first computer of the mail server Exchange 2013 is called mail.cotoso.com, and this is the first time I have seen anyone play like this.

B. Hang 2:

The second mail server Exchange 2013 cannot be deleted properly because the virtual machine for this Exchange 2013 server no longer exists.

C. Hang 3:

The first certificate of mail server Exchange 2013 is issued by this machine. Strange, this is the first time I have seen anyone play like this.

D. Hang 4:

All client import certificates may be those above Exchange 2013.

E. Hang 5:

After upgrading, using foxmail, you can send and receive email from the external network normally.

After upgrading, using Outlook, you can send and receive internal network mail normally, but sending external network mail (barracuda) is rejected, prompting unknown domain names to Exchange 2016.

After the upgrade, the following problems occurred and 2 Exchange 2016 mail servers were shut down.

After shutdown, use Outlook to send and receive external network mail, normal, (barracuda) to the Exchange 2013 server.

F. skip over For further information, please continue to follow this blog update.

5) the end of this blog, normal rest at 23:00, follow-up upgrade completed, and then continued.

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.