StarWind Virtual SAN® Hyper-Converged 3 Nodes Scenario with Hyper-V Cluster

Published: June 2015

This document provides a step-by-step guidance on configuring a hyper-converged 3-node Hyper-V cluster using StarWind Virtual SAN to convert local storage of the Hyper-V hosts into a fault tolerant shared storage resource for Hyper-V. t is intended for experienced Windows system administrators and IT professionals who would like to configure StarWind Virtual SAN solution.

Traditionally, minimal hardware requirement for a fault tolerant Hyper-V failover cluster setup is: 2 Hyper-V hosts, 2 or more servers or SANs to provide shared storage to the cluster and also replicate it in real time for data access redundancy. 3 JBOD Enclosures and proprietary SAS fabric interconnect is required if Clustered Storage Spaces are used as the storage layer, which often makes the setup complex and expensive to implement from both cost and management prospective.

StarWind Virtual SAN® allows users to create a fully redundant, fault tolerant Hyper-V failover cluster and shared storage for it using 2 or 3 Hyper-V hosts and their local storage, without any dedicated storage hardware or proprietary equipment necessary. This introduces an added value compared to the native storage solutions available for Hyper-V.

This document assumes that you have a domain controller and you have added the servers to the domain. It also assumes that you have installed the Failover Clustering and Multipath I/O features, as well as the Hyper-V role on all servers.

The configuration process consists of the following steps:

  • Pre-Configuring the Servers
    • Enabling Multipath Support
    • Configuring Shared Storage
    • Discovering Target Portals
    • Connecting Targets
    • Multipath Configuration
  • Creating a Cluster
  • Adding Cluster Shared Volumes

Related content:

Request a Callback