Exchange 2010 Understanding Storage Configuration
Topic Last Modified: 2010-02-26
This topic describes storage options and requirements for Microsoft Exchange Server 2010. Understanding storage configuration is important to your Mailbox server storage design solution. For additional information about other key aspects of the design process, see Mailbox Server Storage Design.
Storage Architectures
The table below describes supported storage architectures and provides best practice guidance for each type of storage architecture where appropriate.
Supported storage architectures
| Storage architecture | Description | Best practice |
|---|---|---|
|
Direct Attached Storage (DAS) |
DAS is a digital storage system directly attached to a server or workstation, without a storage network in between. For example, DAS transports include Serial Attached SCSI (SAS), Serial Attached ATA. |
|
|
Storage Area Network (SAN): iSCSI |
SANis an architecture to attach remote computer storage devices (such as disk arrays and tape libraries to servers in such a way that the devices appear as locally attached to the operating system (for example, block storage). iSCSI SAN's encapsulate SCSI commands within Internet Protocol (IP) packets and use standard networking infrastructure as the storage transport (for example, ethernet). |
Don't share physical disks backing Exchange data with other applications. Use dedicated storage networks. Use multiple network paths for stand-alone configurations. |
|
Storage Area Network (SAN): Fibre Channel (FC) |
(SAN) is an architecture to attach remote computer storage devices (such as disk arrays and tape libraries to servers in such a way that the devices appear as locally attached to the operating system (for example, block storage). Fibre Channel SANs encapsulate SCSI commands within FC packets and generally utilize specialized Fibre Channel networks as the storage transport. |
Don't share physical disks backing Exchange data with other applications. Use multiple FC network paths for stand-alone configurations. Follow storage vendor's best practices for tuning FC Host Bus Adapters (HBAs). For example, Queue Depth/Queue Target. |
Network Attached Storage (NAS): SMB is an unsupported server architecture. A NAS unit is a self-contained computer connected to a network, with the sole purpose of supplying file-based data storage services to other devices on the network. The operating system and other software on the NAS unit provide the functionality of data storage, file systems, and access to files, and the management of these functionalities (for example, file storage).
Physical Disk Types
The table below provides a list of supported physical disk types and provides best practice guidance for each physical desk type where appropriate.
Supported physical disk types
| Physical Disk Type | Description | Best practice |
|---|---|---|
|
SATA |
SATA is a serial interface for Advanced Technology Attachment (ATA) and integrated device electronics (IDE) disks. SATA disks are available in a variety of form factors, speeds, and capacities. In general, choose SATA disks for Exchange 2010 Mailbox storage when you have the following design requirements:
|
Requires battery backed caching array controller for optimal data reliability and I/O performance. Physical disk-write caching must be disabled when used without an uninterruptable power supply (UPS). When considering SATA disks, we suggest considering "Enterprise class" SATA disks which generally have better heat, vibration, and reliability characteristics. |
|
SAS |
SAS is a serial interface for Small Computer System Interface disks. SAS disks are available in a variety of form factors, speeds, and capacities. In general, choose SAS disks for Exchange 2010 Mailbox storage when you have the following design requirements:
|
Physical disk-write caching must be disabled when used without an UPS. |
|
Fibre Channel (FC) |
Fibre Channel (FC) is an electrical interface used to connect disks to Fibre Channel-based storage arrays (SANs). FC disks are available in a variety of speeds and capacities. In general, choose FC disks fore Exchange 2010 Mailbox storage when you have the following design requirements:
|
Physical disk-write caching must be disabled when used without an UPS. |
|
SSD (Flash Disk) |
A solid-state drive (SSD) is a data storage device that uses solid-state memory to store persistent data. An SSD emulates a hard disk drive interface. SSD disks are available in a variety of, speeds (different I/O performance capabilities) and capacities. In general, choose SSD disks for Exchange 2010 Mailbox storage when you have the following design requirements:
|
Physical disk-write caching must be disabled when used without an UPS. In general, Exchange 2010 Mailbox doesn't require the performance characteristics of SSD storage. |
Factors to Consider in Choosing Disk Types
There are several trade-offs when choosing disk types for Exchange 2010 storage. The correct disk is one that balances performance (both sequential and random) with capacity, reliability, power utilization, and capital cost. The following table of supported physical disk types provides information to help you when considering these factors.
Factors in disk type choice
| Disk speed (RPM) | Disk form factor | Interface/Transport | Capacity | Random I/O performance | Sequential I/O performance | Power utilization |
|---|---|---|---|---|---|---|
|
5.4K |
2.5-inch |
SATA |
Average |
Poor |
Poor |
Excellent |
|
|
3.5-inch |
SATA |
Excellent |
Poor |
Poor |
Above Average |
|
7.2K |
2.5-inch |
SATA |
Average |
Average |
Average |
Excellent |
|
|
2.5-inch |
SAS |
Average |
Average |
Above Average |
Excellent |
|
|
3.5-inch |
SATA |
Excellent |
Average |
Above Average |
Above Average |
|
|
3.5-inch |
SAS |
Excellent |
Average |
Above Average |
Above Average |
|
|
3.5-inch |
FC |
Excellent |
Average |
Above Average |
Average |
|
10K |
2.5-inch |
SAS |
Below Average |
Excellent |
Above Average |
Above Average |
|
|
3.5-inch |
SATA |
Average |
Average |
Above Average |
Above Average |
|
|
3.5-inch |
SAS |
Average |
Above Average |
Above Average |
Below Average |
|
|
3.5-inch |
FC |
Average |
Above Average |
Above Average |
Below Average |
|
15K |
2.5-inch |
SAS |
Poor |
Excellent |
Excellent |
Average |
|
|
3.5-inch |
SAS |
Average |
Excellent |
Excellent |
Below Average |
|
|
3.5-inch |
FC |
Average |
Excellent |
Excellent |
Poor |
|
Solid State Disk (SSD): Enterprise Class |
N/A |
SATA/SAS/FC |
Poor |
Excellent |
Excellent |
Excellent |
Understanding Storage Configuration
This section provides best practice information about supported disk/array controller configurations.
RAID (Redundant Array of Independent Disks) is often used to both improve the performance characteristics of individual disks (by striping data across several disks) as well as to provide protection from individual disk failures. With the advancements in Exchange 2010 high availability, RAID is no longer a required component for Exchange 2010 storage design. However, RAID is still an essential piece to Exchange 2010 storage design for stand-alone servers as well as high availability solutions which require either additional performance or greater storage reliability. The table below provides guidance for the common RAID types that can be used with the Exchange 2010 Mailbox server.
Supported RAID types for Exchange 2010 Mailbox server role
| Data type | Stand-alone: Supported/Best practices | High availability: Supported/Best practices |
|---|---|---|
|
OS/System/Pagefile Volume |
All RAID types supported. Best Practice: RAID 1/10 |
All RAID types supported. Best Practice: RAID 1/10 |
|
Exchange Mailbox Database File (ED |
All RAID types supported. Best Practice: 5.4K/7.2K Disks = RAID1/10 only |
All RAID types supported. JBOD/Raidless supported (3 or more database copies) Best Practice: 5.4K/7.2K Disks = RAID1/10 only or JBOD Best Practice: When lagged, database copies should have either two or more lagged copies or lagged copies should be protected with RAID. |
|
Exchange Mailbox Database Log Volume |
All RAID types supported. Best Practice = RAID1/10 |
All RAID types supported. JBOD/Raidless supported (3 or more database copies) Best Practice = RAID1/10 Best Practice: When lagged database copies should have either two or more lagged copies or lagged copies should be protected with RAID. |
The table below provides guidance about storage array configurations for Exchange 2010.
Supported RAID types for Exchange 2010 Mailbox server role
| RAID type | Description | Stand-alone: Supported/Best practices |
|---|---|---|
|
Disk Array RAID Stripe Size (kb)* |
The stripe size is the unit of data distribution within a RAID set. |
Best Practice: 256KB or greater. Follow storage vendor best practices. |
|
Storage Array Cache Settings |
The cache settings provided by a battery-backed caching array controller. |
Best Practice: 75 percent write cache and 25 percent read cache (battery-backed cache). Follow storage vendor best practices. |
|
Physical Disk Write Caching |
The settings for the cache are on each individual disk. |
Supported: Physical disk write caching must be disabled when used without a UPS. |
The table below provides guidance about database and log file choices.
Database and log file choices for Exchange 2010 Mailbox server role
| Database and log file guidance | Description | Stand-alone: Supported/Best practices | High availability: Supported/Best practices |
|---|---|---|---|
|
File Placement: Database/log isolation |
Database/log isolation refers to placing the database file and logs from the same Mailbox database on to different volumes backed by different physical disks. |
Best Practice: For recoverability, move database file (.edb) and logs from the same database to different volumes backed by different physical disks. |
Isolation of logs and databases isn't required. |
|
File Placement: Database files/volume |
Database files/volume refers to how you distribute Database files within or across disk volumes. |
Best Practice: Based on your backup methodology. |
Supported: When using JBOD, divide a single disk in to two volumes (one for database, one for log stream). Best Practice: When using JBOD, single database per log per volume. |
|
File Placement: Log streams/volume |
Log streams/volume refers to how you distribute database log files within or across disk volumes. |
Best Practice: Based on your backup methodology. |
Supported: When using JBOD, divide a single disk in to two volumes (one for database, one for log stream). Best Practice: When using JBOD, single database per log per volume. |
|
Database size |
The on disk database file size (.edb) |
Supported: Approximately 16 TB Best Practice:
|
Supported: Approximately 16 TB Best Practice:
|
|
Log truncation method |
The process for truncating and deleting old database log files. There are two mechanisms:
|
Best Practice:
|
Best Practice:
|
The table below provides guidance about Windows disk types.
Windows disk types for Exchange 2010 Mailbox server role
| Windows disk type | Description | Stand-alone Supported/Best practices | High Availability: Supported/Best practices |
|---|---|---|---|
|
Basic disk |
A disk initialized for basic storage is called a basic disk. A basic disk contains basic volumes, such as primary partitions, extended partitions, and logical drives. |
Supported Best Practice: Use basic disks |
Supported Best Practice: Use basic disks |
|
Dynamic disk |
A disk initialized for dynamic storage is called a dynamic disk. A dynamic disk contains dynamic volumes, such as simple volumes, spanned volumes, striped volumes, mirrored volumes, and RAID-5 volumes. |
Supported |
Supported |
The table below provides guidance on volume configurations.
Volume configurations for Exchange 2010 Mailbox server role
| Volume configuration | Description | Stand-alone: Support/Best Practice | High Availability: Supported/best practices |
|---|---|---|---|
|
GUID Partition Table (GPT) |
GPT is a disk architecture that expands on the older Master Boot Record (MBR) partitioning scheme. The maximum NTFS formatted partition size is 256 TB. |
Supported Best Practice: Use GPT partitions |
Supported Best Practice: Use GPT partitions |
|
Master Boot Record (MBR) |
A master boot record (MBR), or partition sector, is the 512-byte boot sector that is the first sector ("LBA Sector 0") of a partitioned data storage device such as a hard disk. The maximum NTFS formatted partition size is 2 TB. |
Supported |
Supported |
|
Partition alignment |
Partition alignment refers to aligning partitions on sector boundaries for optimal performance. |
Windows Server 2008 default: 1 MB |
Windows Server 2008 default: 1 MB |
|
Volume path |
Volume path refers to how a volume is accessed. |
Supported: Drive letter or mount Point Best Practice: Mount point host volume must be RAID'ed. |
Supported: Drive letter or mount point Best Practice: Mount point host volume must be RAID'ed. |
|
File system |
File system is a method for storing and organizing computer files and the data they contain to make it easy to find and access them. |
Supported: NTFS support only |
Supported: NTFS support only |
|
NTFS defragmentation |
NTFS defragmentation is a process that reduces the amount of fragmentation in Windows file systems. It does this by physically organizing the contents of the disk to store the pieces of each file close together and contiguously. |
Not required and not recommended. |
Not required and not recommended. |
|
NTFS allocation unit size |
NTFS allocation unit size represents the smallest amount of disk space that can be allocated to hold a file. |
Supported: All allocation unit sizes. Best Practice: 64KB for both .edb and log volumes |
Supported: All allocation unit sizes. Best Practice: 64KB for both .edb and log volumes |
|
NTFS compression |
NTFS compression is the process of reducing the actual size of a file stored on the hard disk. |
Not supported for Exchange database/log files |
Not supported for Exchange database/log files |
|
NTFS Encrypted File System (EFS) |
EFS enables users to encrypt individual files, folders, or entire data drives. Because EFS provides strong encryption through industry-standard algorithms and public key cryptography, encrypted files are confidential even if an attacker bypasses system security. |
Not supported for Exchange database/log files |
Not supported for Exchange database/log files |
|
Windows Bitlocker (volume encryption) |
Windows BitLocker is a data protection feature in Windows Server 2008. BitLocker protects against data theft or exposure on computers that are lost or stolen, and it offers more secure data deletion when computers are decommissioned. |
Supported for all Exchange database and log files |
Supported for all Exchange database and log files |


Comments