Kan man använda JBOD (Just a Bunch Of Discs) i Exchange 2010...

Jupp, detta har jag tagit upp tidigare när det gäller Exchange 2010.  Nu finns det en helt lysande artikel om detta med ett helt drös bilder och liknande.
Artikeln hittar man här:
http://blogs.technet.com/ucedsg/archive/2010/05/06/can-i-really-use-jbod-storage-with-exchange-2010.aspx

Artikeln börjar:
Can I really use JBOD storage with Exchange 2010?

I just did an Exchange 2010 architectural design session for a university in Ohio and this was a key question they asked me. The answer is yes, you truly can leverage JBOD (Just a Bunch Of Disks) storage with large TB SATA drives for Exchange 2010 now. Microsoft IT has deployed Exchange 2010 with JBOD storage and we are benchmarked as some of the heaviest mail profiles available. This proves using JBOD storage with Exchange 2010 can handle even the highest of mail loads/stress and IOPS per user (.11+).

Why would I consider JBOD storage for Exchange 2010?
Storage is going to be your largest expense in deploying Exchange 2010. If you can reduce your storage costs by anywhere from 90%+ to 40%, maintain the same performance, and significantly grow your mail quota per user it becomes a no brainer. This is the same conclusion MS IT came to. They also did not need to grow their storage staff to maintain JBOD.

How is this possible?

Cheap SATA and JBOD storage are possible since, with Exchange 2010, the product team managed to significantly increase and optimize database performance which resulted in reducing the IOPS per user by another 70% over Exchange 2007. This translates to the use of cheaper storage can be leveraged for equivalent performance of higher cost storage used with Exchange 2007.

For example, a 7200RPM 1TB SATA drive will provide an estimated 75-80 IOPS per spindle. This now becomes a viable spindle type for Exchange 2010 with the additional 70% IOPS/mailbox reduction. If you add in our new DAG availability, where we replicate and failover at the database layer, JBOD becomes a viable option as well.

Det är verkligen rekommenderad läsning. Det fanns ett par dragningar om detta på TechEd i November och det är helt otroligt vilket jobb man gjort för att ändra I/O i Exchange...