StarWind Native SAN for Hyper-V as Classic SAN

[hixont]

In my environement my current StarWind SAN servers are pretty beefy and spend much of their time underutilized hardwarewise. Since I have a demand to improve Hyper-V capacity and an insufficient budget to do so quickly I am pondering two scenarios.

The first is to add Hyper-V to my existing SAN servers in order to tap into their mostly unused resources (RAM and CPU) and continuing to use them as SAN servers. Other than needing additional NICs (which I already have) what are the downsides to this option?

The second option is to convert over to the Hyper-V native StarWind SAN software. I would still have four external Hyper-V cluster servers needing iSCSI SAN services in addition to the two Native Hyper-V servers. Is this viable?

In both scenarios I would have a six server Hyper-V cluster, two of which are acting as the SAN servers in addition to being Hyper-V cluster servers.

[anton (staff)]

It's absolutely possible to use StarWind Native SAN for Hyper-V not only to cross-feed but also feed other Hyper-V hosts with shared storage.