MS Exchange
Step 1
Identify the requirements
1. Business requirements
a. Capabilities
i. Internal email services
ii. External email services
iii. Connectivity for external users
iv. Public folders
v. Unified communication services
b. Portion of organization
c. Business isolation
i. Legal isolation
ii. Political environment
iii. Regulatory requirements
iv. Business policy
d. Operational consolidation
e. Unified global address list
f. Any business policies impact messaging usage
g. Internal hygiene services
h. Availability requirements
Functional area High availability required
Mailbox access – access to an individual mailbox
Mailbox access for external users
Internal message flow – email within the organization
External message flow – email outside of the organization
Message hygiene – antimalware and antispam
Voice mail access
2. Technical requirements
a. Messaging services used by Forests and domains
b. Physical locations and requirements
c. Message hygiene requirements
d. Existing messaging services statistics (use log monitoring)
Step 2
Messaging service instances
1. Minimum instance is one, or
2. Multi-instances are deployed if
a. Merges and acquisition
b. Subsidiaries/business unit separation
c. Regulatory and/or legal requirements
3. Complex consideration need for multiple Active Directory forests and/or external business relationship
Step 3
Mail server infrastructure
1. Role placement
a. Administrative and security requirements
b. Site autonomy
c. Fault-tolerance dependencies
2. Capacity
a. Individual database size
i. White space requirements
mailboxes No. X average send and receive mails per day
ii. Transport dumpster size
1.5 X maximum message size limit
iii. Mailbox recoverable items time window
(daily incoming/outgoing mail x average message size X deleted item retention window) +(mailbox quota size x 0.012) + (mailbox quota size x 0.058)
b. Log file size
i. Log capacity
Log file size per day X days before replay X (1+20%)
ii. Traditional backup and restore effects
Log file size X number of databases X days retention
iii. Differential backups
Larger than an entire week of log file space for both backup and replay
iv. Mailbox resiliency backup effects
3 X log file size per day
c. Users per database
d. Databases per server
e. Databases per location
f. Servers per location
g. Available open databases for fault tolerance
3. Performance
a. Processor cores
i. Megacycles required per mailbox = 1 megacycle per each 50 messages sent and/or received per day
ii. Total megacycles required = total number of mailboxes x megacycles per mailbox
iii. Processor cores = megacycle requirement / processor core megacycle capacity
iv. Megacycles per socket = number of cores per socket x megacycles per core
v. Processor sockets = total number of megacycles required / megacycles per socket
b. Memory
Memory required = 4 GB base RAM + ROUNDUP(# databases / 10) * 2 +
(# messages per day / 50 * 3 MB)
c. Disk
IOPS per mailbox = 0.060 x (number of messages sent/received per day / 50)
4. Fault tolerance
Step 4
Client Access Server Infrastructure
1. Role placement
2. Capacity
No requirement for storage because it is stateless
3. Performance
a. Processor cores
3 Client Access server processor cores for every 4 Mailbox server processor cores
Workload CPU cost (MHz/user)
Outlook (MAPI) 0.35
Outlook Anywhere 0.80
Exchange ActiveSync 1.60
Exchange Web Services (Microsoft Entourage) 0.71
Outlook Web App (OWA) 0.86
IMAP4* 0.86
POP3* 0.33
*IMAP4 and POP3 protocols do not support sending new mail, so the observed costs do not reflect any sent messages within the user profile.
i. Total Client Access server computing megahertz (MHz) required = total number of client connections x CPU cost per client
ii. Processor cores = megahertz requirement / processor core megahertz capacity
iii. Processor cores = greater of the two calculations
iv. Total sockets required = processor cores / platform capabilities
b. Memory
2GB per processor core
c. Disk
Not required
d. Network
Workload Network cost (KB/sec/user)
Outlook (MAPI) 0.37
Outlook Anywhere 0.44
Exchange ActiveSync (delta from Outlook) 1.04
Exchange Web Services (Microsoft Entourage) 0.54
Outlook Web App 0.88
IMAP4* 0.14
POP3* 0.79
*IMAP4 and POP3 protocols do not support sending new mail (this is accomplished via SMTP through Hub Transport servers), so the observed costs do not reflect any sent messages within the user profile.
Total Client Access server network throughput required = total number of client connections x network cost per client
4. Fault tolerance
Step 5
Hub Transport Server Infrastructure
1. Role placement
2. Capacity
a. Message tracking space
700MB per day for a week, total is 4.9GB
b. Protocol log space
2.7GB per day for a week, total is 18.9GB
c. Transaction log space
>=500MB
d. Database size
Average message X maximum queue
e. Replicated mail database space
Enough space for dumpster to store in-transit messages for all replicated mailbox databases
f. Buff space
20% more
g. Disk free space
>=500MB
3. Performance
a. Processor cores
i. No antivirus present: 1 Hub Transport processor core for every 7 Mailbox server processor cores.
ii. Antivirus present: 1 Hub Transport processor core for every 5 Mailbox server processor cores.
b. Memory
1GB per core
c. Disk
Align with messaging server
d. Network
Not required
4. Fault tolerance
Step 6
Hub Transport Server Infrastructure
1. Role placement
2. Capacity
h. Message tracking space
700MB per day for a week, total is 4.9GB
i. Protocol log space
2.7GB per day for a week, total is 18.9GB
j. Transaction log space
>=500MB
k. Database size
Average message X maximum queue
l. Replicated mail database space
Enough space for dumpster to store in-transit messages for all replicated mailbox databases
m. Buff space
20% more
n. Disk free space
>=500MB
3. Performance
a. Processor cores
i. No antivirus present: 1 Hub Transport processor core for every 7 Mailbox server processor cores.
ii. Antivirus present: 1 Hub Transport processor core for every 5 Mailbox server processor cores.
b. Memory
1GB per core
c. Disk
Align with messaging server
d. Network
Not required
4. Fault tolerance
Step 7
Edge Transport Server Infrastructure
1. Role placement
a. Geographic location
b. Network connectivity requirements
2. Capacity
o. Message tracking space
100MB per day for a week, total is 700MB
p. Protocol log space
2.7GB per day for a week, total is 18.9GB
q. Transaction log space
>=500MB
r. Database size
Average message X maximum queue
s. Replicated mail database space
Enough space for dumpster to store in-transit messages for all replicated mailbox databases
t. Buff space
20% more
u. Disk free space
>=500MB
3. Performance
a. Processor cores
i. Connection per second
ii. Message per second
iii. Average message size
b. Memory
1GB per core
c. Disk
Align with messaging server
d. Network
Not required
4. Fault tolerance
Step 8
Unified Messaging Server Infrastructure
1. Role placement
a. Connectivity
Round-trip time between IP gateway and UM server < 300 ms
b. Administrative and security requirements
c. Site autonomy
d. Fault-tolerance dependancies
2. Capacity
Immediately forward to Hub Transport server, disk requirements are minimal.
3. Performance
a. Processor cores
i. Two processor sockets
ii. Sizing processor cores based on voice mail preview
iii. Adding additional servers based on concurrent call volumes
b. Memory
2GB per core
c. Disk
Not sensitive
d. Network
i. Place PBXs physically close to IP gateways.
ii. Place IP gateways and UM servers on the same well-connected network or within the same physical site.
iii. Place UM servers on the same well-connected network or within the same physical site as other computers that have Exchange Server 2010 server roles installed, including Mailbox, Hub Transport, and Client Access servers.
iv. End WAN connections close to where telephony equipment is located.
v. In branch office scenarios or over WAN connections, use the G.723.1 codec instead of the G.711u or G.711A codec to minimize the network traffic that is passed between IP gateways and UM servers.
4. Fault tolerance
a. UM server failure
b. IP gateway failure
No comments:
Post a Comment