The Exchange Mailbox Server role is arguably one of the most important roles within an Exchange deployment for it stores the data that users will ultimately access on a daily basis. Therefore, ensuring that you design the mailbox server role correctly is critical to your design.
With Exchange 2010 you can deploy a solution that leverages mailbox resiliency and has multiple database copies deployed across datacenters, implements single item recovery for data recovery, and has the flexibility in storage design to allow you to deploy on storage area networks utilizing fibre-channel or SATA class disks or on direct attached storage utilizing SAS or SATA class disks with or without RAID protection. But, in order to design your solution, you need to understand the following criteria:
- User profile – the message profile, the mailbox size, and the number of users
- High availability architecture – the number of database copies you plant to deploy, whether the solution will be site resilient, the desired number of mailbox servers
- Server’s CPU platform
- Storage architecture – the disk capacity / type and storage solution
- Backup architecture – whether to use hardware or software VSS and the frequency of the backups, or leverage the Exchange native data protection features
- Network architecture – the utilization, throughput, and latency aspects
Read more at source: http://msexchangeteam.com/archive/2009/11/09/453117.aspx
Technorati : Exchange Server 2010, Storage Calculator
Del.icio.us : Exchange Server 2010, Storage Calculator
Zooomr : Exchange Server 2010, Storage Calculator
Flickr : Exchange Server 2010, Storage Calculator
