3208 Views 2 Replies Latest reply: Jan 8, 2010 9:03 PM by Michael Card
By the nature of your questions it sounds like you're trying to "cheap out" on X-SAN. This is a recipe for disaster. An X-SAN requires a minimal level of dedicated resources that you seem unwilling to commit to. Perhaps this is NOT the solution for you. There are other "SAN IN A CAN" solutions out there that may better match your budget.
What are the "SAN IN A CAN" alternatives you refer to here? Do you have any links/product names you can refer me to?
Why is it a recipe for disaster? What do you mean here by "disaster"? Suboptimal performance?
What we want to do is get concurrent access from multiple threads running on multiple cores in our Xserve to the VTrak without having the threads "bottleneck" at the disk. Maybe running the VTrak in the DAS configuration is better, perhaps X-SAN really only helps when you have multiple Xserves as "clients" in the SAN.
Certainly we had not budgeted for 2 Xserves to be used as MDCs and needing to buy a 3rd to actually run our application.
Is there anyone reading this thread who could tell me what the performance of 1 Xserve running a 16 TB VTrak as a DAS would be vs. an Xserve client accessing the VTrak over XSan? Perhaps Xsan really only "buys you something" when you have multiple Xserves hooked into the SAN but it really doesn't buy you anything when you just have multiple cores accessing the SAN from 1 Xserve...