Not sure if this the right place, but hopefully there's someone here who can point me in the right direction...
We're looking at totally renewing our Hyper-V environment, which is currently living on some aging servers and an EVA SAN. All in need of replacing. Obviously we'll be moving to server 2012, and SMB 3.0 has caught our eye. It stacks up really well against the iSCSI SANs we've been looking at, possibly more flexible, and a lot more cost effective. There's some quite impressive videos out there on what SMB 3.0 can deliver, but I haven't yet found one which addresses our scenario.
We're looking to create a Hyper-V cluster which spans two physical locations, so the storage (File server cluster / iSCSI SANs) will also need to span to both locations. This is all in case one physical location goes down, for example fire. The file server host/SAN in each location will have it's own attached storage, but will be clustered with the other location, and the combined storage will be mirrored.
The only snag is, the only scenarios I've seen for SMB 3.0 is where the underlying storage for a File Server Cluster has to be available to all the nodes of the cluster.
I'm probably approaching this all wrong, so I'm opening it up for any ideas...
Andrew France - http://andrewsprivatecloud.wordpress.com