Hi all,
I'm new to StarWind and we have project we're looking to do with it. Am I correct in understanding that Virtual SAN actually is supposed to be installed directly on the Hyper-V parent/host, rather than on a child/guest Windows VM hosted on the parent/host?
I just wanted to make sure I understand this clearly.
And my follow up questions to this would be:
1.) Does this not create issues with Microsoft tech support, since they don't want the Hyper-V parent/host to be shared with other server roles?
2.) How does this work with RAM cache? I suppose we'd need to be sure to have enough RAM in the parent for:
a.) The VMs we plan to run on the Hyper-V host.
b.) Whatever amount of RAM cache we wish to use with Virtual SAN, I'm guessing there's a way to statically define this (we don't want Virtual SAN fighting with Hyper-V for resources)?
Thanks for your time & help!
Sincerely,
-
Doug Mortensen
Impala Networks
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software