We plan to build a failover storage with Windows2012r2. There will be 2 or 3 physical machines with 2 virtual machines on each server. One virtual machine building a failover, second one being storage machine (storage + failover machine on each physical server).
The network layout looks like this: Click for bigger image.
On storage machines I plan to create storage pools (with tiering and mirrored) and iSCSI virtual disks that will be provisioned to failover machines (one disk on each storage machine). I have created such cluster in my laboratory with vmware (failover cluster working), but I am posting here in hope to get some advice on following considerations:
If network looks like above, with Dell Force managing all the traffic and 6 NICS on each physical server node (2x10 Gb and 4 x 1Gb) what would be the best way to utulize them? Or even is that setup a reasonable one (I know there will be SPOFs)?
How would you set up the storage pools and failover later, to have data mirrored on each storage node, and how would it affect perfromance? What would be the most optimal setup for such setting (not to loose too much usable space)?
If I have 64 gigs of ram on each physical node, which virtual machine should have more ram. The one with storage or the failover ones to achieve good performacne?
I'll appreciate all insight from people who've done similar things.
(please move the comments or answers, thanks)
You can indeed cluster Microsoft iSCSI on top of an existing shared storage.
What you do you make a config which will die with every node of cluster died. Because target images are not synchronized between each other.
...or draw a correct interconnection diagram :)
To answer above:
Actually I've managed to create Scale Out File Server (clustered) with those 3 virtual ISCSI disks connected to cluster server. I've created mirrored virtual disk on the pool (formed from the virtual iSCSI) and added that to cluster. Then created SOFS. Then I switched the server with one of the virtual iSCSI's off (plugged the power off)- the cluster and the share on it was working. The cluster reported one disk missing but the cluster was not offline. Then I repowered the storage and it reconnected to cluster.
I see what you do now finally! OK, the problem is Microsoft does not support anything except SAS in production within a Clustered Storage Spaces for a reason. See:
"The clustered storage pool MUST be comprised of Serial Attached SCSI (SAS) connected physical disks. Layering any form of storage subsystem, whether an internal RAID card or an external RAID box, regardless of being directly connected or connected via a storage fabric, is not supported."
Aidan had did it ages ago and we did it as well. See:
What you do is not going to work reliably. Unfortunately. It's a pity Microsoft had removed non-SAS filter with R2 and did forget to provide warning.