StarWind Virtual SAN Hyper-Converged 2 Nodes Scenario with Hyper-V Cluster

Published: August 2016

StarWind Virtual SAN is a hardware-less VM storage solution, which creates a fault-tolerant and high-performing storage pool for the virtualization workloads by mirroring existing server’s storage and RAM between the nodes of the storage cluster. The storage resource, created this way, is treated just as local storage by all hypervisors and clustered applications. For High Availability, the multipath access to all storage nodes is provided. The technical paper is an instruction for experienced Windows Server users or system administrators on how to setup 2 node HyperConverged Hyper-V Cluster with StarWind Virtual SAN as a storage provider. This is done to increase the availability of the services or applications and exclude the downtime during the maintenance. The steps described include pre-configuring servers, creating the cluster, and adding Witness and Cluster Shared Volumes. Pre-configuring servers is done in several smaller steps. A domain controller must be defined, and the servers must be added to it. Then, Failover Clustering and Multipath I/O features, as well as the Hyper-V role are installed on both servers. First, StarWind Virtual SAN must be downloaded, installed and registered. It may be installed according to one of the following types:

  • StarWind Virtual SAN Server (recommended);
  • StarWind Virtual SAN Service, designed for Core OS editions;
  • StarWind Management Console.

At the next stage of installation, an appropriate license key must be selected: a time-limited fully functional evaluation key, a FREE version key, or a fully commercial license key. The next step is configuring shared storage, which is implemented with the help of StarWind Management Console. Then, the default storage pool must be specified. All the devices created through the Add Device wizard will be stored on it. Next, virtual disks are created at StarWind servers, with specifying location, name, size, and options for them. After, they are attached to the target, and the second HA node is added. Synchronous two-way replication is configured. The previously created disks are connected to the servers, which will be added to the cluster. The targets are connected and multipath is configured. With the Server Manager, the cluster is created. After that, Witness and Cluster Shared Volumes can be added, the latter being necessary to work with Hyper-V virtual machines. Once the disks are added to the cluster shared volumes list, it becomes possible to create highly available virtual machines on them.

Related content: