just take your favorite PCIe SAS RAID controller and toss it in a Thunderbolt 2 PCIe enclosure. (None are presently shipping, but Sonnet is offering free Thunderbolt 2 upgrades on their current models and those could very well land before the new Mac Pro.) That gives you the same options for cheap enclosures you have with SAS, except you can easily move your SAS controller between systems and use it with laptops. This is the solution we've decided on. (Although I'm investigating just biting the bullet on iSCSI/10GbE or FC SAN.)
That'll work fine, as long as your card only has 1 port or doesn't mind throttling down to 4x PCIe2.0. TB2 is only 20Gbps, whereas MiniSAS with 3.0 can handle 24Gbps per port.
The nMP literally doesn't have enough TB2 bandwidth to run 4 ports of MiniSAS all at once.
What a joke that the old Mac Pro, PCIe 2.0 and all, is capable of more storage throughput than the new one.
----------
That's true, and I myself run a huge external array (using inexpensive eSATA and an inexpensive PC case with high-quality PSU). I was just pointing out that nMP owners will be forced to externalize more of their storage. For many, this adds significant expense and/or risk. Also, even for external options I prefer the old Mac Pro. PCIe (eSATA or MiniSAS) is just so much cheaper than thunderbolt controllers and even USB3 at present for external arrays.
Internal storage becomes irrelevant past a certain point because even on the most (internally) expandable systems it is, ultimately, pretty limited. When individual projects can run to multiple terabytes, and you might need access to old projects at any time (i.e. you can't just archive them off and never look at them again), external storage, typically either external RAID or some sort of SAN solution, becomes the only sensible option. All of our machines have had no job-specifc data (except perhaps tiny project files) stored on internal storage for years — including on old Mac Pro and on Wintel systems where there's plenty of room for such storage. The new Mac Pro just reflects what we've been doing anyway.
Last edited: