Virtual SAN Free new installation

[jmarce]

Dear all,

first of all, thank you very much to all of you.
I'm newbie with StarWin and also not so expert in Windows Server, but I have to create a failover system to virtualize with two similar servers. I have only the Windows 2016 server license (not the datacenter) so I decided to use a Virtual SAN free to have a failover storage system and a failover hyper-V through windows server settings.

I have tried to create the HA storage through the scripts, but the same script in one server always fails and in the second it creates something, but synchronization does not run.

So I tried through the console, but when I tried to create the replica I can't select the network interface. I tried to add in the server management but nothing. So after all I uninstalled everything to try to start from scrach.

Any advice or help to do that? I just want to create a great 1.7 TB disk to allocate in it the Virtual Machines of the Hyper-V cluster.

Any help will be wellcome.

Thank

[Ivan (staff)]

Dear jmarce,
Thanks for your interest in StarWind solution.
Could you share with us the error in PowerShell when you trying to create StarWind device?
Also, I would recommend you to remove server role "File and iSCSI Services" -> "iSCSI Target Server"/"iSCSI Target Storage Provider". Could you check your firewall as well, 3260 and 3261 ports should be allowed on both servers.

[jmarce]

Dear all,

I'm still having problems with the installation.
I uninstall everything of Virtual SAN in both servers and reinstall again. Now my problem is that through the Console I can't create a replicated device because there isn't any network interface in the list. I tryed to add it in the Console--> Server--> Configuration tab but nothing happens, only the 127.0.0.1 interface appears.

So I'm really frustrated with it, and it makes me try other sollutions. We are able to purchase the complete license to have support and the console as well, but if I can't put the service running, and make a test of failover over a hyper-v cluster that I need, it will be impossible that I can recommend it.

Of course any help will be wellcome. And also I thank to everybody that have read this post and will try te help me.

Maybe a Windows server 2016 issue with network devices or not. As I said, any help is welcome.

Thanks to everybody

[Sergey (staff)]

Dear jmarce, thank you for your question. According to StarWind system requirements https://www.starwindsoftware.com/system-requirements you need at least 3 network interfaces: 1 for Management, 1 for iSCSI connection and 1 for synchronization between nodes. I would recommend you to build the system with StarWind Management Console first. Let me provide you with a step-by-step guide for a hyper-converged 2-nodes scenario with Hyper-V cluster:

https://www.starwindsoftware.com/techni ... manual.pdf

Network interfaces might be missing because of a third party app installed that uses port 3260. The most common app is MS iSCSI Target Server which can be accidentally installed along with File and Storage Services pack. MS iSCSI Target Server can be uninstalled via Server Management Console > Manage > Remove Roles and Features > Server Roles > iSCSI Target Server. Any other software that uses port 3260 should be uninstalled as well. After this StarWind service must be restarted.

Please try to follow the guide from the link above step-by-step and let me know if you need any assistance.