Oops. I must have had a free license file generated in the short window that it was available for bare-metal Hyper-V clusters. Sorry for the bad information.

Branin

Ahh. I stand corrected. :- )

Sure, it's a free beer, mate. You just have to come with your own mug. Use free Microsoft's hyper-v server as a host OS for you physical hosts, create two VM's and install StarWind in it. Works like a charm. This is incorrect. I'm running the free version on 2 physical Hyper-V hosts just fine (I ha...

The problem is that the free version of StarWind can not be installed directly on bare-metal servers in the 2-node configuration. The only way to use such scenario with a free version is to create a Hyper-V VM on each server and install StarWind into it. This is incorrect. I'm running the free vers...

It is not possible to install free version of StarWind to initial hardware servers for a 2-node configuration. It can be installed only inside Hyper-V VM's. The solution is to create a VM on each server and install free version of StarWind into it. This is incorrect. I'm running the free version on...

I've saved some logs from my Cluster, if that helps at all. I see a bunch of "MountTargetDll failed with error code 1627!" errors at the end, but am not sure if they are a cause of my problem or a symptom. NW-VMHOST01 is the node that I'm keeping up (and downloading the logs from), while N...

If it helps at all, I'm seeing lines like the following in my Cluster log (get-clusterlog) for one of the CSVs. The other one sometimes transitions fine and other times fails. 00001068.00001e00::2015/06/04-17:42:46.431 INFO [RES] Physical Disk : SetDiskInfo(2) 00001068.00001e00::2015/06/04-17:42:46....

Everything is mostly going great, except I have an high availability problem. :- ( Basically, I followed the directions exactly and have 2 nodes with 2 CSVs total and 1 VM on each of the CSVs (for testing purposes). I can move the VMs and CSVs between nodes all day long, without issue. I can shutdow...

Thank you very much!

Branin

When I connect it only once, I get the warning message in Failover Cluster Validation about only having a single path to the witness disk. How do I keep Failover Cluster Validation happy with only having one connection to the Witness disk? (The CSV1 and CSV2 disks are correct and working great.) Tha...

If I set up my witness with three connections as such: On NW-VMHOST01: NW-VMHOST01-WITNESS, connecting to: 127.0.0.1, 172.16.120.1 (connecting via 172.16.120.1 [yes, the same IP]), 172.16.125.1 (connecting via 172.16.125.1 [yes, the same IP]) and on NW-VMHOST02: NW-VMHOST02-WITNESS, connecting to: 1...

I'm confused. How can I connect twice to the witness, but only with localhost? For example, on my first node (NW-VMHOST01), I'm connected to: NW-VMHOST01-WITNESS: 127.0.0.1 NW-VMHOST01-CSV1 and NW-VMHOST02-CSV1: 127.0.0.1, 172.16.120.2, 172.16.125.2 (the .2 addresses are on my second node, connected...

I'm creating a 2-node cluster as outlined https://www.starwindsoftware.com/starwind-virtual-san-hyper-converged-2-nodes-scenario-2-nodes-with-hyper-v-cluster, and attempting to follow the directions as exactly as possible. However, I'm running into 2 small issues: 1) Page 13 says to essentially repe...

Hello! Approximate time for this release to come out is 4 weeks. Dedup on thick images was always disabled, so i am not sure i understand your question. Although, you could enable Windows deduplication for thick images. Is this 4 more weeks from today? Back on May 01, the ETA was 2 weeks, which is ...

Thank you very much for your recommendation. However, it appears the downsides to thick provisioning include lack of support for the hardware VSS provider (to increase backup efficiencies) as well as deduplication. Do you still recommend thick provisioning even with those limitations? Thank you! Bra...