StarWind Virtual Storage Appliance Installation Guide with VMware vSphere

Published: April 2017

StarWind Linux-based Virtual Storage Appliance allows users who don't want to change their current infrastructure to quickly deploy StarWind to test features and functionality. StarWind is now releasing the new Linux version, compatible with all industry-standard hypervisors: Microsoft Hyper-V, VMware ESXi, Xen and KVM. Additionally, StarWind Virtual Storage Appliance incorporates StarWind vCenter plugin to make it more convenient for VMware users. StarWind VSA is easy in deployment and management.

This guide describes the deployment and configuration process of the StarWind Virtual Storage Appliance with VMware vSphere. The deployment requires two components: StarWind Virtual Storage Appliance and Linux virtual machine that has StarWind installed and configured.

StarWind Virtual Storage Appliance VM requires at least 4 virtual processors with 2 GHz reserved, at least 4 GB of RAM, 3 NIC ports dedicated as separate vSwitches for management, StarWind synchronization and iSCSI traffic to ensure the proper functioning of VSA. The first step is downloading the zip archive that contains StarWind Web Management Appliance and extraction of VM files. Next, the virtual machine must be deployed to the vSphere.

To do this, the location of the OVF template must be indicated and VSA files selected. Next, the name, location, storage and networks for the StarWind VSA VM must be selected. After this, the deployment process can be started.

By default, StarWind VSA virtual machine will receive IP address automatically via DHCP. It is recommended to create a DHCP reservation and set a static IP address for this VM.

After the installation is complete, a new virtual disk must be added to the StarWind VSA VM. Next step is logging into StarWind Virtual Storage Appliance and connecting to the StarWind VSA via IP address, which VM had received via DHCP. Next, the new volume for VSA Storage can be created.

Finally, Synchronization, Management and iSCSI IP addresses for each NIC can be assigned. After this, the preconfiguration process is finished.

Request a Callback