Dave, Correct, if you want to use direct links for StarWind ISCSI and synchronization on three-nodes setup, you need at least 5 NICs in total, 2 for StarWind synchronization, 2 for iscsi each and 2 for sync each plus at least 1 for your VMs management. You can use switch, but you should be aware tha...

You should be able to shrink thin-provisioned vmdk with the help of VMware functionality.

Could you please collect the logs using this tool?
Please log a support case using the form.
Regarding Witness drive, 1 Gb should be enough. You can just simply create a new StarWind HA device and change Witness in the Cluster.

Hello!
Could you please provide the logs from StarWind V2V Converter for checking?

Thank you for sharing your experience.

Since you are using directly connected cables between servers for StarWind ISCSI and synchronization, the main requirement will be to use different subnets and vSwitches on ESXi level for each of the direct connections. . You are assigning IPs from this subnet for network connections inside StarWind...

Hello Dave, Yes, you can use the IPs according to the diagram. Regarding StarWind Management Console, you can download and install one on the Windows-based machine and connect to StarWind from the console. Please select StarWind Management Console and Integration Component Library during installation.

Hello,
Thank you for the update. If the issue persists, please proceed with the steps I have provided.

Hello midnight,
According to MPIO policy cache should be in use on both nodes.
Could you please collect the logs using this tool?
Please log a support case using the form.

Could you please collect and send us the logs one more time, after changes you did?

Thank you for confirming. Please let us know if you will see anything wrong.

Hi,
I guess you are using x86 Windows 10 OS on your machine.
StarWind V2V Converter can be installed only to x64 OS.

Could you please collect the logs and share with us for checking?
Please use this tool for collection.

Yes, StarWind is stopping synchronization in case of problems with underlying storage in order to prevent problems on production level. You can see events about read/write delays in StarWind log in that case.
And yes, the storage part should be checked as the first option.
Nope

Could you please give more details?
What subnet are you using for StarWind synchronization? Is that link directly connected or connected via Switch?
Do you have the same network settings on both hosts, Jumbo frames, etc?