StarWind Virtual SAN Compute and Storage Separated 2 Nodes with Hyper-V Cluster

Published: July 2015

This document contains a step-by-step guide for creating and configuring StarWind Virtual SAN Compute and Storage Separated on 2 dedicated servers (Nodes) to provide fault tolerant shared storage to a client hypervisor cluster.

Usually, minimal hardware requirement for a fault tolerant Hyper-V failover cluster setup is 2 Hyper-V hosts and at least 2 servers or SANs which will 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. This 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 just the 2 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.

A configuration with a dedicated SAN layer gives customers the ability to provide both block level and file level storage to the clients, resulting in a unified SAN/NAS solution which can be used for different applications and virtualization environments at the same time. It also allows users to configure StarWind Virtual SAN as a gateway to consolidate their heterogeneous storage environment into a single storage resource pool. Backend SANs can be a mix of different SANs from different vendors using different storage media like FC and iSCSI.

This guide is intended for experienced Windows system administrators and IT professionals who would like to configure a hyper-converged Scale-Out File Server cluster using StarWind Virtual SAN to convert the local or iSCSI attached storage of the cluster nodes into a fault tolerant shared storage resource to be then presented to the client servers using SMB3 file share protocol.

Pre-requisites:

This document assumes that you have already configured Active Directory and added two servers to the domain. It also assumes that you have installed the Failover Clustering, Multipath I/O features (enabled for iSCSI devices for example using MPIO manager), and the Hyper-V role on the both servers.

Configuration process consists of the following steps:

  • Pre-Configuring the Servers
  • Creating Virtual disk (WITNESS, CSV1, CSV2)
  • Adding Discover portals
  • Connecting Targets
  • Creating a Cluster
  • Adding Cluster Shared Volume

Related content: