Administrator's Guide
IMPORTANT: You must run these tools in a non-production environment to avoid potential loss
of data and performance degradation.
For more information about these tools, see Tools for Performance and Scalability Evaluation at
http://technet.microsoft.com/en-us/library/dd335108.aspx. If you are testing Jetstress, only the
E5000 servers are required. The servers must not have Exchange loaded when running Jetstress.
When running LoadGen, Exchange server 2010 SP1 is installed on both servers in the E5000
enclosure, and the Client Access Server, Hub Transport Server, and Mailbox Server roles are
installed. Because multiple roles are installed on both servers, and because of the participation of
each server in the Database Availability Group (DAG), you must use an external load balancing
method. Two possible methods are the following:
• Use a hardware load balancer.
• Use Exchange database configuration to balance load across the CAS servers manually.
◦ MAPI Traffic: Assuming the users are evenly split between databases, use the
Set-MailboxDatabase cmdlet available from Microsoft at
nl
http://technet.microsoft.com/en-us/library/bb123971.aspx and specify the
rpcclientaccessserver parameter equal to cas1 for half the databases and cas2
for the other half.
◦ OWA Traffic: OWA requires persistence, so direct all OWA traffic through the first CAS.
◦ Exchange Sync (EAS): Direct all OWA traffic through the second CAS.
◦ Other protocols (POP3, IMAP, and so forth): use DNS round-robin to get rudimentary
load balancing.
36 Configuring the messaging system software