REF: Exchange 2010 - Exchange Performance (Part 1)

-

 

1. CAS 有大量RPC client access，CAS請準備充足的CPU Core & MEM
2. Mailbox:HUB ---> 5:1 (with AntiVirus Scanning)
3. Mailbox:CAS ---> 4:3 (很高的比例)
4. Mailbox role 上，每個處理器核心，處理基準為500U
5. 建議佈署兩部HUB & CAS

image

image

在上述比率中，必須注意這是處理器核心的比率，不是處理器的比率。因此，計算比率時，雙核心處理器會算成 2。

Dd346701.note(en-us,EXCHG.140).gifImportant:

The Mailbox to Client Access server role ratios detailed in the chart above contains recommendations based on the Exchange 2010 feature, RPC Client Access. This feature requires a larger memory and processor configuration to manage the increase loads placed on the Client Access server role. The RPC Client Access feature is enabled by default.

When considering these recommendations, be aware of the following:

  • The preceding ratios are a general rule, and they may not be valid for every topology. A general rule means that the ratios are not a requirement for support or a definitive rule.
  • Ratios can change dramatically based on user profiles. A user that creates a larger than expected load against the Mailbox server role than the Hub Transport server role will increase the Mailbox:Hub ratio, and vice versa.
  • These recommendations are derived from the internal deployment of Mailbox servers at Microsoft, which is based on approximately 750 heavy users per processor core.
  • These ratios assume that Mailbox servers are at greater than 60 percent processor utilization during peak periods, with corresponding processor utilization on Hub Transport or Client Access servers.
  • For these recommendations, the processors used on Mailbox, Hub Transport, and Client Access server roles were the same type and speed.
  • A minimum of two Hub Transport and two Client Access servers should be deployed for redundancy and to ensure uninterrupted service in case of planned or unplanned server downtime.
  • The Hub Transport server role ratio that includes antivirus scanning was obtained using Microsoft Forefront Security for Exchange Server with five active scanning engines.
  • The Client Access server role ratio includes using Secure Sockets Layer (SSL) for all access protocols.


  • 上述比率是一般規則，可能並非所有拓撲皆適用。一般規則的意思是該比率並非是支援需求或強制規則。
  • 比率可依據使用者設定檔動態變更。使用者對 Mailbox server role 建立的負載量若大於預期的 Hub Transport server role 負載量，將會增加 Mailbox:Hub 比率；反之亦然。
  • 這些建議衍生自 Microsoft 的 Mailbox Server 內部部署，以每個處理器核心大約 500 名大量使用者為基礎。
  • 這些比率假設 Mailbox Server 在尖峰時段的處理器使用率大於 60%，Hub Transport Server 或 Client Access Server 上具有相對應的處理器使用率。
  • 就這些建議而言，在 Mailbox、Hub Transport 及 Client Access server role 上使用的處理器類型和速度皆相同。
  • 必須至少部署兩部 Hub Transport Server 及兩部 Client Access Server 以供備用，並確保在計畫和非計畫的伺服器停機時，不會中斷服務。
  • 您可以使用適用於 Microsoft Operations Manager 2005 Service Pack 1 (SP1) 的 Exchange 2007 管理組件，以及效能疑難排解員 (位於 Exchange 管理主控台的 [工具箱] 節點中)，根據效能判斷特定部署是否需要其他伺服器角色。這些工具亦可用來微調特定部署的伺服器角色比率。如需 Exchange 2007 管理組件的相關資訊，請參閱使用 Microsoft Operations Manager 2005 SP1 監視 Exchange 2007。如需效能疑難排解員的相關資訊，請參閱使用工具箱。
  • 您可以使用具有五個主動掃描引擎的 Microsoft Forefront Security for Exchange Server，來取得包含防毒掃描功能的 Hub Transport server role 比率。
  • Client Access server role 比率包括對所有存取通訊協定使用安全通訊端層 (SSL)。


Blog Extended Reading

1. REF: Exchange 2010 - Exchange Performance (Part 2)

More Information & Reference

1. Understanding Server Role Ratios and Exchange Performance
2. 規劃伺服器角色比率 (Exchange 2007)

Radiohead22_thumb53

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c7992...
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Secti...
Read more

Ticket: RemoteAPP certificate revocation check error

-
Image
  . certutil -f –urlfetch -verify <your_certificate>.cer From internet client (Win7 ultimate x64) Issuer:     CN=TWCA Secure CA -Evaluation Only     OU=SSL Certification Service Provider-Evaluation Only     O=TAIWAN-CA INC.     C=TW Subject:     CN=deep2.msft.com     OU=ITS     O=Msft Corporation     L=Taipei     S=Taiwan     C=TW Cert Serial Number: 04bd dwFlags = CA_VERIFY_FLAGS_ALLOW_UNTRUSTED_ROOT (0x1) dwFlags = CA_VERIFY_FLAGS_IGNORE_OFFLINE (0x2) dwFlags = CA_VERIFY_FLAGS_FULL_CHAIN_REVOCATION (0x8) dwFlags = CA_VERIFY_FLAGS_CONSOLE_TRACE (0x20000000) dwFlags = CA_VERIFY_FLAGS_DUMP_CHAIN (0x40000000) ChainFlags = CERT_CHAIN_REVOCATION_CHECK_CHAIN (0x20000000) HCCE_LOCAL_MACHINE CERT_CHAIN_POLICY_BASE -------- CERT_CHAIN_CONTEXT -------- ChainContext.dwErrorStatu...
Read more