The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
I agree that the problem doesn't look like a StarWind specific issue, but rather some interaction between the Virtual SAN Software, Windows itself and my hardware. Unfortunately, I'm only using the free version, so I don't get access to the StarWind auto-configuration team (as great as that would be). I'm going to continue trying different things to try to resolve the issue and if I ever do, I'll post back here.bubu wrote:I hope you agree with me that it does not look like StarWind related issue. And I understand that MS support might not be helpful since StarWind is installed. MS and StarWind might point each other (sorry guys ), but as far as I know StarWind guys troubleshoot even indirect issues that are not related to their software during the installation assistance wich they offer after purchase. Basically, they configure everything from scratch and leave a customer happy.
If I were you, I would not trade High Availability for Hyper-V Replicas.
It's up to you
I believe I was able to "fix" this particular issue with the previous build (i.e. before 8116 and the L2 cache functionality), through 1 of 2 different mechanisms (or possibly both).Vitaliq (staff) wrote:Branin,
May I wonder if there are any updates than those described here https://forums.starwindsoftware.com/vie ... f=5&t=4274 ??
Jim,Tourwinner wrote:Branin-
Earlier in the thread, it was mentioned that you connect the opposite witness to pass the failover cluster validation. If you connected those targets (connected to witness2 from node1 and witness1 from node2), make sure that they are disconnected from the Targets tab and also removed from the Favorites tab on the opposite nodes after the validation test (i.e. witness2 is disconnected and removed from the favorites tab on node1 etc.)
Also, make sure that MPIO for each target is set to Failover Only and the Active connection is set to 127.0.0.1 and the other connections are set to Standby.
We had this identical problem when we first set it up in a three node cluster. Once we worked with support, they showed me the error of our ways and we fixed it to great success. We now have four clusters successfully deployed and tested fully (plug pulling, planned failover, cluster aware updating etc.) It just works now (thank God....)
If it is setup like I described above, then the problem is something else I can't readily identify.
Good luck,
Jim