It’s been many months since I have written a update on the SAN build.
Basically, the Openfiler box is running 16 x 3TB Seagate ST3000DM001 6G SATA drives (no these are not enterprise class drives… I know that), with a QLA2562 dual port 8Gb HBA and has been rock solid as a FC target. It runs 24/7 and so far has a longest up-time of 43 days, and I only restarted it then for a check-up, but there was really no need.
The storage is currently configured RAID 1+0 for redundancy because I was worried about the hard drives being kicked out of the array due to error correction time-outs (considering these are not enterprise drives), but not one of the 16 Seagate Barracuda 3TB desktop drives has even threatened to give me a issue in over three months on the Areca controller so now I want to reconfigure it to RAID 5. I feel I can trust it now.
I ditched SANmp very early on as it did not provide me with concurrent read/write access from multiple clients simultaneously. Since then I set up XSAN 2.3 on Lion using a older spare Mac Pro as a metadata controller running Lion Server, with three clients (one of which is also a back-up MDC) all running Lion or Lion Server. These are all Mac Pro workstations with LSI 7204 4Gb dual port HBAs.
Setting up XSAN correctly is a bit too involved to get into in this post, but needless to say I had to provide a separate private gigabit switch and network for XSAN metadata, and completely reconfigure our entire network with a existing Windows 2008 R2 server providing carefully and correctly configured DNS, DHCP and Active Directory services. I’ve built this whole system buying the absolute minimum (buying re-conditioned when I have to buy) and using or re-purposing as much as I could that we already had.
The Windows server is running on a rock solid HP Proliant ML350 G6, and I needed to set up our LTO5 drive (running LTFS) on Windows rather than OSX anyway. To be fair I didn’t have many issues binding the Macs to a Windows hosted Active Directory so I’ve had no issues there.
Apple XSAN is a complex and frustrating beast. However it works well once it is set up correctly. I’m getting +/- 330MB/sec read and write to the SAN from all clients, it’s currently approaching 80% full, and as I said, the Openfiler box has been the least of my issues… in fact it hasn’t been a issue at all. It is completely transparent to XSAN, it might as well be a Promise VTrak as far as the end performance and usability is concerned.
I know anyone wanting to replicate this will need for technical information. I will post more of the nuts and bolts asap.
























