StarWind Virtual SAN Compute and Storage Separated Multi-Node Cluster Scale-Out Existing Deployments for VMware vSphere

Published: August 2014

This document provides a step-by-step guidance on scaling out the hyper-converged 2-node StarWind Virtual SAN that converts the storage resources of the separated general purpose servers into a fault tolerant shared storage resource for ESXi. It is intended for experienced StarWind users, VMware and Windows system administrators and IT professionals who would like to add the Scale-Out node to the StarWind Virtual SAN® cluster.

Traditionally VMware requires having some sort of the shared storage to guarantee the data safety, allow the virtual machines migration, enables continuous application availability and eliminates any single point of failure within IT environment. VMware users have to choose between two options when choosing the shared storage:

  • Hyper-Converged solutions, that allows sharing the same hardware resources for the application (i.e. hypervisor, database) and the shares storage, thus decreasing the TcO and achieving the outstanding performance results
  • Compute and Storage separated solutions that keeps the compute and storage layers separately from each other, thus making the maintenance easier, increasing the hardware usage efficiency and allows building the system accurately for solving the task

The document contains a solution diagram as well as description of the configuration process includes following stages:

  • Replacing Partner for (DS2)
  • Creating Virtual Disk (DS3)
  • Configuring ESXI Cluster
    • Configuring the iSCSI Initiator

StarWind Virtual SAN Compute and Storage Separated Multi-Node Cluster Scale-Out Existing Deployments for VMware vSphere

Related content:

Request a Callback