Hi Guys,
We have a HP LeftHand SAN at the minute, with two controllers/enclosures in Server Room A, and the other two in Server Room B.
I'm looking into the idea of replacing this with some x86 tin and Windows Server 2012 R2 Storage Server, using Storage Spaces and Scale-out File Server.
With the LeftHand SAN, the 4 nodes are managed as a single logical unit, where I can provision LUN's which are accessed by my Hyper-V hosts using iSCSI. One of the big advantages of the LeftHand is what they call "network RAID".
This means that as well as having RAID10 done within one of the disk enclosures/controllers, the same data is also mirrored and striped over another (or multiple) enclosures. Therefore traditional RAID will protect me from a disk failure inside of a single
enclosure, but also if a whole enclosure was to totally break then there's another copy of the data on another enclosure (or spread across the rest of the enclosures) and the LeftHand SAN serves that up - with the Hyper-V host being none the wiser.
I'd like to do the same with Windows Server 2012 R2 and Storage Spaces / Scale-out File Server features.
So I'm thinking of having a Windows 2012 R2 server, connected to a JBOD disk enclosure via SAS. This will be done in each server room, giving me 2 servers and two enclosures in total.
What I don't quite understand, is how I can essentially perform "network RAID". E.g. should a single server or enclosure fail or even a whole server room blow up, then the data should be accessible from the other server room.
The reason for my confusion is that the Windows server in Server Room A, won't have a SAS connection to the disk enclosure in Server Room B. Each enclosure is connected only to one Windows Server.
So without shared storage between the two SoFS, is my goal achievable? AFAIK I think all SoFS's will require CSV's... :(
Is there not another way to get around this situation? I can't be the only person who has two server rooms and would like to use Windows as my SAN and have my data stored in both server rooms.
Would replication be another option maybe? But for Hyper-V and/or SQL I'm assuming it would result in locked files and then having to rename "backup" SoFS to the same as the broken one if it came down to it. E.g. no automated failover.
Attached a diagram to try and explain the configuration I was thinking of - but if SoFS require CSV's then I guess I'm out of options and it's a non-starter...? Back to buying HP LeftHand SAN's then...! :(
Thanks - Steve
![]()