So far I've managed to get the HAImage1 / masterimg21 on server CL1 marked as SyncStatus=1, and this did allow me to make the local iSCSI connection on CL1 to masterimg21, and also allowed the remote connection from CL2 to masterimg21. However I still can't get either CL1 or CL2 to connect iSCSI to ...

Server 2019 core, Hyper-V clustering, 2-node I believe some firewall rules caused a loss of connectivity and devices got out of sync. Firewall is opened up and there are no drops occuring now. Node1 holds MasterImg21 which the event logs on both nodes list as most recently marked fully synchronized ...

Cluster networks settings question - guide wasn't too clear on which networks can be used for Cluster / Cluster and Client communication. I have Synch, iSCSI, Management, and IPv6 link local listed in my Networks. Currently I only have Management set to allow Cluster and Client, the rest are all set...

There is a CreateHA script mentioned herein. You cannot create HA for an img file. Since it is just a witness, create a new 1 GB HA, connect it as described here and connect it as a witness in cluster. Once you connect the HA (witness), remove old target and file. ^^^ THIS!! I had though the HA dev...

Thank you for your question. It is necessary to create a HA device for wiitness I used CreateImageFile.ps1 so apparently I did not create a HA device. That makes sense. I looked in the CreateHAPartnerWitness.ps1 and it appears to be for creating a whole 3 node environment from nothing. Is there a s...

Based on that validation finding I just went ahead and did connect to the witness disk from CL2, it popped up in available disks and was able to be added to the quorum selection, and now CL1 and CL2 are each showing 1 vote. Witness disk is now online as Cluster Disk 2, assigned Disk Witness in Quoru...

Make sure to connect the witness disk only locally. You can extend the device with the ExtendDevice script from C:\Program Files\StarWind Software\StarWind\StarWindX\Samples\powershell. Ok so I do need a witness in this 2 node. I was a bit confused by the witness part earlier since documentation se...

Great info thanks. The network requirements wording in the setup guide makes a lot more sense with that context. So far I have: Created devices with Create_HA2.ps1 Connected the iSCSI links on both ends Validated and created the Failover Cluster Now I am about to extend the storage. Can you point me...

I mean that I put the management network in as a second heartbeat now. So since that is on the built in NIC, rather from the add-on NIC which has both iSCSI+HB and Sync, I am in now configured to avoid split-brain with just the two adapters, correct?

Each server has a builtin physical adapter with 4x 1Gbit ports. NIC1 on both hosts are port 1 of this and this is the management network. Each server has an add-on physical adapter with 2x 10Gbit ports, NIC5 iSCSI+HB and NIC6 Synch are ports 1 and 2 respectively on this. Would you please clarify her...

I am attempting to set up a POC of HA 2 node Hyper-V cluster on Server Core 2019 using "CreateHA_2.PS1" but am getting this error. I'm not clear on what to do with some of the addresses in the script. (edit: I followed this to stage the servers -- https://www.starwindsoftware.com/resource-...