Exchange 2010 Storage Guidance

May 14, 2010

in 2010, Exchange, Microsoft

Below is a matrix put together by the Exchange product team displaying their recommended guidance for Exchange 2010 storage.

Exchange 2010 Storage GuidanceStand AloneDAG: 2 nodes, 2 Database copiesDAG: 3+ nodes, 3+ Database copies
Storage Type
Direct Attached Storage (DAS)SupportedSupportedSupported
Storage Area Network (SAN): iSCSISupported. Best Practice = Do not share physical disks backing Exchange data with other applications.Supported. Best Practice = Do not share physical disks backing Exchange data with other applications.Supported. Best Practice = Do not share physical disks backing Exchange data with other applications.
Storage Area Network (SAN): Fibre Channel (FC)Supported. Best Practice = Do not share physical disks backing Exchange data with other applications.Supported. Best Practice = Do not share physical disks backing Exchange data with other applications.Supported. Best Practice = Do not share physical disks backing Exchange data with other applications.
Best Practice = Do not place both database copies on the same physical spindles.Best Practice = Do not place both database copies on the same physical spindles.
Network Attached Storage (NAS): SMBNot SupportedNot SupportedNot Supported
Physical Disk Type
SATASupported, requires battery backed caching array controller for data integritySupported, requires battery backed caching array controller for data integritySupported, requires battery backed caching array controller for data integrity
SASSupportedSupportedSupported
FC/FATASupportedSupportedSupported
SSD (Flash Disk)SupportedSupportedSupported
Physical Disk Write Caching (enabled)Not SupportedNot SupportedNot Supported
Storage RAIDRAID recommendedRAID recommendedRAID optional
EDB VolumeRAID5/6, RAID10, RAID1RAID5/6, RAID10, RAID1JBOD, RAID5/6, RAID10, RAID1
Log VolumeRAID1, RAID10RAID1, RAID10JBOD, RAID1, RAID10
Disk Array RAID Stripe Size (kb)256KB256KB256KB
Storage Array Cache Settings75% Write Cache, 25% Read Cache (with Battery Backed Cache)75% Write Cache, 25% Read Cache (with Battery Backed Cache)75% Write Cache, 25% Read Cache (with Battery Backed Cache)
Database/Log file placement
Database/Log IsolationBest Practice (for recoverability) = separate database file (.edb) and logs from same Database on to different volumes backed by different physical disksDatabase file (.edb) and logs from same Database can share same volume and same physical disk.Database file (.edb) and logs from same Database can share same volume and same physical disk. This is a best practice for JBOD/RAID'less storage scenario where one or more volumes store the edb and log files backed by the same physical disk.
Database Files/VolumeBased on backup methodologyBased on backup methodologyRAID = based on backup methodology, JBOD = one DB file/volume is recommended
Log Streams/VolumeBased on backup methodologyBased on backup methodologyRAID = based on backup methodology, JBOD = one log stream/volume is recommended
Windows Disk Type
Basic DiskRecommendedRecommendedRecommended
Dynamic DiskSupportedSupportedSupported
Partition Type
GUID Partition Table (GPT)RecommendedRecommendedRecommended
Master Boot Record (MBR)SupportedSupportedSupported
Partition AlignmentWindows 2008 Default: 1MBWindows 2008 Default: 1MBWindows 2008 Default: 1MB
Volume PathDrive Letter or Mount Point (mount point host volume must be RAIDed)Drive Letter or Mount Point (mount point host volume must be RAIDed)Drive Letter or Mount Point (mount point host volume must be RAIDed)
File SystemNTFS support onlyNTFS support onlyNTFS support only
NTFS DefragmentationNot required, not recommendedNot required, not recommendedNot required, not recommended
NTFS Allocation Unit Size64KB for both edb and log volumes64KB for both edb and log volumes64KB for both edb and log volumes
NTFS CompressionNot Supported for Exchange Database filesNot Supported for Exchange Database filesNot Supported for Exchange Database files
NTFS Encrypted File System (EFS)Not Supported for Exchange Database filesNot Supported for Exchange Database filesNot Supported for Exchange Database files
Windows Bitlocker (volume encryption)Supported for all Exchange database and log filesSupported for all Exchange database and log filesSupported for all Exchange database and log files
4,284 views
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...
Rogier [MS] September 15, 2010 at 6:00 am

Comment on Bitlocker und DAG:

From: http://technet.microsoft.com/en-us/library/ee8327

Windows failover clusters can't have BitLocker enabled.
For DAG we NEED failover clustering. With Failover Clustering we cannot enable it, so we cannot use it.

mdrooij March 25, 2011 at 5:05 am

There's a hotfix for that http://support.microsoft.com/?kbid=2446607