Simulate Exchange 20 disk I/O load on a server to verify the. Microsoft Exchange Server Jetstress 2013 Tool. It is highly recommended that the Jetstress user read through the tool. The Dell PC Advisor Personalize your PC with this valuable business tool. Deciding which PC to buy can be challenging, especially when you have unique business requirements that your computer must support.
Instead, it’s just a collection of rules of thumb that will, hopefully, speed up this specific part of the planning process of the different Exchange server roles. Figure 1: Exchange 2. Server Roles. General Guidelines. Although CPU and memory play a crucial role in performance, increasing any of these 2 doesn’t necessarily mean a faster system. The following table shows the recommend memory and CPU for single role servers and for multiple role servers: Role. Recommended. Max Processor Configuration Recommended. Processor Configuration. Recommended. Max Memory Configuration. Recommended Memory Configuration. Hub Transport. 12 cores. GB1 GB per core or 8. GB (minimum)Client Access Server 1. GB2. GB per core or 8. GB (minimum)Mailbox. GB4. GB plus 2- 1. MB per mailbox. Unified Messaging. GB2. GB per core or 4. GB (minimum)Multiple Role Server. GB8. GB plus 2- 1. MB per mailbox. Table 1. Microsoft License Advisor. Use License Advisor to research Microsoft Volume Licensing products, programs and pricing. Get a full quote that you can share with colleagues or your reseller. 1 Select Country/Region and. Dell; Gateway; HP; Lenovo; Toshiba; learn about memory. Crucial Advisor tool If you know your system's specs. Choosing the right Exchange 200X. Exchange 2010 advisor. There are also some role ratio guidelines that should be met: CAS : Mailbox. It’s one of the three mandatory roles (the other ones are CAS and Hub) and it’s where all the user data will be stored. Before entering technical details, I strongly advise you to use the Exchange 2. Mailbox Server Role Requirements Calculator to size the Mailbox role. If you prefer to do it manually, then continue reading. User profile usually determines resource requirements, but you should take into account some factors that influence sizing, such as: Number of mailboxes. Security/auditing mechanisms. Use of mobile devices. Outlook mode (online/cached). Archiving/Messaging Record Management. High Availability (DAG)CPUEstimated Per- Mailbox CPU Consumption: Messages Sent+Receivedper mailbox per day (~7. KB average message size)Megacycles for active or stand- alone mailbox(increase by 1. Megacycles for passive mailbox. Table 3. Memory. To size the necessary amount of RAM, first determine the amount of required database cache by multiplying the mailbox count by the memory requirements based on the user profile. The following table provides estimated values of database cache per mailbox, based on message activity: Messages Sent+Receivedper mailbox per day (~7. KB average message size)Database cache per mailbox (MB)5. Table 4. After determining the database cache size, the next step is to determine the necessary RAM per server to ensure the database cache size requirements can be met. Server Installed Physical Memory. Database Cache Size (Mailbox Role Only)Database Cache Size (Multi- role)2. GB5. 12. MBNot supported. GB1. GBNot supported. GB3. 6. GB2. GB1. GB1. 0. 4. GB8. GB2. GB1. 7. 6. GB1. 4GB3. GB2. 4. 4. GB2. 0GB4. GB3. 9. 2. GB3. 2GB6. GB5. 3. 6. GB4. 4GB9. GB8. 2. 4. GB6. 8GBTable 5. For example: 1. 00. MB per mailbox): 1. MB = 3. GB. 3. GB fits in 3. GB default cache. Deploy 8. GB of RAMNetwork. Gbit minimum. DAG - each server should have at least two networks: a single MAPI network and a single Replication network. Disk. The storage for the Mailbox role must be sized for. Capacity (GB). Performance (IOPS)Capacity is sized based on user mailbox size (read Understanding Mailbox Database and Log Capacity Factors for details on required overhead). Mailbox Size = Mailbox Limit + Whitespace + Dumpster. Performance sizing is based on user profile (message activity). Database Volume I/O = Number of Mailboxes x IOPS Profile. The following table provides per mailbox estimated IOPS based on user profile and message activity. Messages Sent+Receivedper mailbox per day (~7. KB average message size)Estimated IOPS: Single database copy. Estimated IOPS: Multiple database copies. Table 6. Hub & Edge Role. CPUWith A/V and A/SWithout A/V and A/SRecommended processor cores / server 8 4 Hub Cores : mailbox server cores ratio. Table 7. Memory. 4GB min, 8. GB max. 1. GB/core. Disk. Use battery- backed write cache disk controllero Disk I/O can be a bottleneck on an un- tuned Hubo Log I/O becomes virtually free with a BBWC controller. Size storage capacity for queue requirements. Capacity = average message size x maximum queue. Separate mail. que and logs from system disks (RAID 1. Back Pressure: 5. MB minimum free space. Network. CAS Role. CPU and memory are key for CAS. Performance impact on CAS server is dependent on user profiles and mix of workloads. CPU and memory scale guidance for CAS based on assumptions of a mixed- protocol heavy information worker profileo Consider other workloads and adjusto Remember all MAPI traffic now affects CAS. Use Windows Server 2. R2 for best CAS scaleo Major improvements in rpcproxy (Outlook Anywhere)CAS Workload Relative Cost Comparison. Workload. CPU Cost (MHz/user)Network Cost (Kbytes/sec/user)Outlook. Outlook Anywhere. Exchange Active. Sync(delta from Outlook)1. Exchange Web Services (Microsoft Entourage)0. Outlook Web Access. IMAP4*0. 8. 60. 1. POP3*0. 3. 30. 7. Table 8. CPU2 core minimum. Up to 1. 2 cores. CAS: Mailbox cores. Memory. 2GB/core. GB min, 1. 6GB max. Disk. There are no special needs regarding the disk subsystem. Network UM Role. CPU and network are key for UM. Scale out UM servers based on concurrent call requirements. Size CPU based on requirements for Voice Mail Preview: ~1 message/min/core. TCO. Default 1. 00 concurrent calls/server (inbound or outbound)CPU2 core minimum. Up to 1. 2 cores. Memory. 2GB/core (4. GB minimum). 8. GB maximum. Disk. UM doesn’t have significant storage requirements. Network. Virtualization. Since virtualization is becoming popular in Exchange deployments, here are a few guidelines and recommendations: Validating the Solution. Before putting your newly sized servers in production, maybe you want to spend some time validating the deployed configuration. There are some tools from Microsoft that can help you with that task: Microsoft Exchange Server Jetstress. Jetstress simulates the Exchange database and log file loads produced by a specific number of users, thus allowing you to verify the performance and stability of your disk subsystem before putting your server into a production environment. This workload can be used to evaluate how Exchange performs, and can also be used to analyze the effect of various configuration changes on Exchange behavior and performance while the system is under load. The documentation for Load. Gen describes how to configure and execute a load test against an Exchange server. Load. Gen is capable of simulating Microsoft Office Outlook 2. Outlook 2. 00. 7 (online and cached), POP3, IMAP4, SMTP, Active. Sync, and Outlook Web App client activity. It can be used to generate a single- protocol workload, or these client protocols can be combined in some form to generate a multi- protocol workload. The collected data can be used for such tasks as analyzing the performance and health of a server that has mailboxes, improving capacity planning models, and improving testing methodologies and tools. Below you can find some of these tools from 2 of those hardware vendors (descriptions taken from the vendors’ website). Dell Exchange 2. 01. Advisor – The Dell Exchange Advisor tool is subject to change without notice and is provided as- is without warranty of any kind, express or implied. Dell does not make any representations regarding the use, validity, accuracy or reliability of the tool or the results of the use of the Tool. The entire risk arising out of the use of this tool remains solely with the customer. In no event shall Dell be liable for any direct, consequential, incidental, special, punitive or other damages, even if Dell is negligent or has been advised of the possibility of such damages, arising from use of the tool or the information provided herein. This tool is not for use by or for Individual/Consumer purposes. HP Sizer for Microsoft Exchange Server 2. Microsoft. HP has developed the HP Sizer for Microsoft Exchange Server 2. Exchange Server 2. The algorithms developed and implemented in this tool are based upon extensive testing of Exchange Server 2. HP’s deep experience with Microsoft Exchange, and intricate knowledge of server CPU, memory, and I/O subsystems. This tool is free to download and use, and is designed to simplify configuration across a broad range of deployments. This newest Microsoft Exchange Server Sizer provides support for multiple site deployments, varied client types and access methods, all Exchange Server 2. Database Availability Group (DAG) high availability options, choice of tower, rack mounted, or HP Blade. System server platforms, and either direct attached or SAN- based storage solutions. Based on your input, the tool provides a comprehensive bill of materials along with a deployment overview of the Exchange Server 2. Once this Sizer is installed, updates can be downloaded automatically to the underlying software engines that are necessary to provide support for HP server and storage product information details. Conclusion. Exchange sizing and performance tuning can be a complex job, fortunately there are several tools provided by Microsoft and third- parties that can assist you with that task. Although manually sizing an Exchange infra- structure can be fun, my advice is to use all the technical tools available, but always with the vague knowledge of the algorithms that support them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |