If not, repeat procedure for all your servers.
I`ll add another server (10.10.10.7) to cluster while I`m at it | Add ServerĮnter IP, Port for second server (remember ports, because you won’t be able to connect)| Nextįinish if you are done. Specify Cluster name (choose something that suits you) |Nextįirst I`ll add localhost from which I started installation ( 10.10.10.6 ) and port 3260 |NextĬhoose Sync and heartbeat interfaces | Next (if you have errors here, you can choose Sync and heartbeat setting for your public network and heartbeat only for private network) Start StarWind Management Console (it is in your system tray, Start Menu or Desktop)Ĭhoose Clusters from left menu and click on Create new Cluster in right window
STARWIND FREE ISCSI TARGET INSTALL
You can install single installation of Starwind Virtual SAN and it will work as iSCSI Target but you`ll still have storage as single point of failure. So, you will need at least two machines which will host Starwind Virtual SAN in order for it to make sense.
STARWIND FREE ISCSI TARGET WINDOWS
HyperV machine with Windows Server 2012 R2 STDĢNICs: LAN: 10.10.10.6 Private: 192.168.1.10ĭisk config: Windows system disk C:\ and disk that will store Starwind virtual disk E:ĢNICs: LAN: 10.10.10.7 Private: 192.168.1.11Īdditional machine on which we`ll attach created virtual disks via iSCSI initiator Machines that are hosting Starwind Virtual SAN: One additional virtual machine will be used for trying and testing storage what we created with Starwind Virtual SAN Free. On every physical server inside HyperV is VM based on Windows Server 2012 R2 STD that will host Starwind Virtual SAN, one VM for every physical server.
Two separate servers with Windows Server 2012 R2 STD and HyperV installed on each. I`ll be configuring Starwind Free SAN to work in cluster with HA storage.įor this you`ll need to buy license, or if you plan to use only 2 nodes you can get them free, just send email to them, and you`ll receive one.
In first article about Starwind Free SAN I covered installation of app.
0 kommentar(er)
