how to setup 2 node cluster with clustered Storage - Hyper V

[disto]

Hi all,

I'm new with StarWind Virtual SAN.
I try to setup a test environment with 2 Windows 2012 R2 Hyper-V Servers.
Both of them have only local storage. I'd like to setup a clustered storage with Virtual SAN to provide HA Storage to a Hyper-V Cluster.
I've created a Cluster and added the 2 server. Then i did "create clusterd storage". After I added the server with available store and klick next, I get the error "Storage creation failed. Failed: invalid partner info."
On one of the server a imagefile1 has been created on the local storage, on the other server nothing was created.

Is there any documentation of how to setup a storage cluster? Can anyone provide some information please?

best regards

[Oles (staff)]

Hello Disto!

Yes, we have a quick start guidance for setting up Hyper-Converged with Hyper-V Cluster 2 Nodes Scenario, it can be found here:
https://www.starwindsoftware.com/starwi ... -v-cluster

[disto]

Hi Oles,

thank you for that.
Well that's the way I expected it. And I will do this as described in the document.

But what about the "Cluster"-section within StarWind Virtual SAN on the left side?
What is it for? I can't find anything about that in the help.

Thanks for your support

best regards

[Oles (staff)]

Disto,

You may configure everything from Cluster section now, but it is still in development. So my recommendations on this would be, to configure everything in Servers section.
Also, there is no guidance on configuring from Clusters section yet, but we are working on it.

[bigflyer]

One problem I had when following that guide, is that right at the end, when creating the Windows failover cluster, in step 5 it shows "add all eligible storage to the cluster" as checked. When I did that, Windows decided to add ALL the drives to the cluster, so all the drives where the Virtual SAN img files were stored were added to the cluster (on both nodes), so Starwind Virtual SAN couldn't access them any more, so the HA devices all failed instantly. It ended up in a mess...

If I do it again, I'll uncheck that box, and add the storage to the cluster manually!

[anton (staff)]

Sounds like it should not do this way... We'll check it out and we'll update manual if confirmed! Thank you for reporting

One problem I had when following that guide, is that right at the end, when creating the Windows failover cluster, in step 5 it shows "add all eligible storage to the cluster" as checked. When I did that, Windows decided to add ALL the drives to the cluster, so all the drives where the Virtual SAN img files were stored were added to the cluster (on both nodes), so Starwind Virtual SAN couldn't access them any more, so the HA devices all failed instantly. It ended up in a mess...

If I do it again, I'll uncheck that box, and add the storage to the cluster manually!

[Anatoly (staff)]

One problem I had when following that guide, is that right at the end, when creating the Windows failover cluster, in step 5 it shows "add all eligible storage to the cluster" as checked. When I did that, Windows decided to add ALL the drives to the cluster, so all the drives where the Virtual SAN img files were stored were added to the cluster (on both nodes), so Starwind Virtual SAN couldn't access them any more, so the HA devices all failed instantly. It ended up in a mess...

If I do it again, I'll uncheck that box, and add the storage to the cluster manually!

Hi~ I`m a bit confused. Can I ask you what page are you refering to please?

[bigflyer]

Hi~ I`m a bit confused. Can I ask you what page are you refering to please?

Page 29, first image, step 5 of 'Creating a Cluster'. The 'add all eligible storage to the cluster' box is checked.

(from https://www.starwindsoftware.com/starwi ... -v-cluster)

It may be that our Windows 2012R2 decided to do something odd and add ineligible storage to the cluster as well (I admit I wasn't expecting non-shared storage to be added), but that's what happened...

[Anatoly (staff)]

Got it. OK, we will consider making changes there.
Thank you for the input.