For each database use its own database LUN and its own transaction log LUN
Independent LUNs offer better perfomance, disk corruption error isolation…
![Exchange database transaction logs disks](https://somoit.net/content/images/2015/12/Exchange-database-transaction-logs-disks-300x282.jpg)
Depending on your disk and exchange environments, maybe this configuration means too many LUNs.
A single LUN for each database+logs is also a good choice.
Use volume mount points
To avoid using lots of drive letters use mount points as it is fully supported by Exchange
![Configure volume as mount points](https://somoit.net/content/images/2015/12/Drive-mount-point.jpg)
![Folder used as a mount point](https://somoit.net/content/images/2015/12/Mount-points.jpg)
Use GPT partition table (instead of MBR)
![Disk partition style GPT](https://somoit.net/content/images/2015/12/Disk-partition-style-GPT.jpg)
You can only configure the partition style when the disk has no volumes. Dont forget to check (and change to GPT if the partition is MBR) before configuring volume, exchange database…
![Disk partition style MBR](https://somoit.net/content/images/2015/12/Disk-partition-style-MBR.jpg)
![Disk partition "Convert to GTP Disk" option](https://somoit.net/content/images/2015/12/Disk-partition-convert-to-GPT.jpg)
NTFS allocation Filesystem should be 64K
When formatting the newly created volumes, choose 64K for allocation unit size
![Format volume with allocation unit size 64K](https://somoit.net/content/images/2015/12/Format-volume-64K.jpg)