Exchange Server 2010 Learning (10) Typical Exchange Server high availability planning

In the previous series, we focused on how small businesses implement the installation, Setup, and basic management of exchange Server2010. Starting today, we will discuss how to achieve high availability of Exchange server in a midsize enterprise environment, and build a typical high-availability environment in the hope of meeting the communications needs of the general enterprise as much as possible.

Active Directory Planning

Exchange 2010 requires that the minimum operating system version of an Active Directory domain controller/global catalog server Run is Windows Server 2003 SP2, with a minimum domain and forest functional level of Windows Server 2003, The minimum operating system version currently used in this case is the Windows Server 2003 R2 SP1, and the Active Directory will be built again. Therefore, the requirements for the Active Directory service are fully compliant with Exchange 2010.

Architecture Logic Planning

According to the customer's actual situation, need to meet 2000 of users of the mail communication needs, to ensure the stability of the mail system, reliability and high availability. After understanding the customer requirements, the first thing to do is the Exchange Server2010 schema logic design, which will use the following server roles:

Client Access server: The role supports Outlook Web Access, Outlook Anywhere, and Exchange ActiveSync client applications, as well as clients of the POP3 and IMAP4 protocols. The Client Access server role also provides other key services, such as Autodiscover Server and Exchange Web service. Note that the Client Access server role must be installed in each Active Directory site that has a mailbox server deployed, with only one ad site in this case.

Hub Transport server (Hub Transport): This color is used to process all mail flows within an organization, apply transport rules, apply journaling policies, and deliver messages to recipients ' mailboxes. The Hub Transport server role provides features such as internal mail flow, external mail flow, messaging policies, and anti-spam and antivirus protection.

Mailbox Server (Mailbox): This role is critical to hosting mailbox databases, providing richer calendar features, resource management, and offline address book downloads.

The Edge Transport server role and the Unified Communications Server role are not considered for use. Deploy two (CAS role +hub role) servers for high availability with NLB, deploy two MBX roles, and use the database high-availability group DAG mechanism in Exchange Server 2010 systems to enable high availability of mailbox server roles.

Server hardware Planning

CPU Capacity Planning: We first look at the mailbox server CPU capacity planning, assuming that the active database is evenly distributed on two nodes, then ideally, each server should host 1000 (2000÷2) active mailbox. However, when a failure occurs, a node will host 2000 active mailboxes. Per mailbox to send or receive 150 messages per day calculation using 3MHZ calculation, the active mailbox CPU demand is 2000*3mhz=6000mhz, that is, about 6GHz. Each increase in a database copy this value is multiplied by 10%, in this case, each database has an active copy and a passive copy, so the 6000MHz is added 10% (6000 * 1.1 = 6600MHz). Each passive mailbox uses approximately 0.45MHz, so the CPU requirement for the passive mailbox is: 2000*0.45=900mhz. Therefore, the total CPU demand used in this example is 6600mhz+900mhz=7500mhz, so as long as the CPU is purchased, it is recommended that the standalone server be designed to be a CPU with a usage rate of not more than 70% during the peak period.

For CPU capacity planning for the Client Access server role and Hub Transport role, refer to the following table:

Server role Ratios	Recommended processor Core ratios
Mailbox: Hub	7:1 (no antivirus scanning in hub) 5:1 (There is antivirus scanning in the hub)
Mailbox: Client Access	4:3
Mailboxes: Client Access and Hub mix roles	1:1

Users may run Active Directory on either the x86 platform or the x64 platform (64-bit), the recommended rate for the Active Directory directory server processor core and Exchange 2010 Mailbox Server Processor core is 1:4---1:8.

The above reference is based on: http://technet.microsoft.com/zh-cn/library/ee712771 (v=exchg.141). aspx.

Memory capacity Planning: After understanding the approximate number of processor cores required by each server role, Microsoft also gives memory capacity recommendations. The following table lists the minimum supported memory configurations and recommended memory configurations for different Exchange 2010 server roles. The minimum memory configuration specifies the minimum memory configuration that is appropriate for the Exchange 2010 server. The minimum hardware requirements must be met to obtain support from Microsoft customer service and support; the highest memory configuration is the recommended memory configuration for a specific server role. The recommended maximum configuration is defined as the upper limit of the available processor and memory configuration for both price and performance. The recommended maximum configuration is a benchmark. It is not a support standard, and it does not consider resource requirements for Third-party applications that might access the server or install on the server. The recommended maximum configuration may change over time as well as price changes and technological advances. The following table lists the minimum supported memory configurations and recommended maximum memory configurations for different Exchange 2010:

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/Mail/

The above reference is based on: http://technet.microsoft.com/zh-CN/library/dd346700 (v=exchg.141). aspx.