1
SPECIFICATIONS

System Requirements

To ensure the promised performance and stability, the systems running StarWind solutions must meet the minimum system requirements that are listed below.

2
StarWind Virtual SAN | VSAN

StarWind Virtual SAN (VSAN) for Hyper-V VSAN for Hyper-V

CPU

Minimum one physical 1.7 GHz processor

RAM

4GB
If using cache or Asynchronous Replication, an appropriate amount of RAM should be added

Network

Heartbeat failover strategy:
2x network interfaces (1xStarWind Synchronization and 1xiSCSI traffic/Heartbeat) + 1x network interface (Management/Heartbeat)
At least one Heartbeat interface must be on a separate network adapter and redundant

Node Majority failover strategy:
2x network interfaces (1xStarWind Synchronization and 1xiSCSI traffic) + 1x network interface (Management/Witness node)

Network Bandwidth

Synchronous Replication: Minimum 1 GbE or higher

Latency requirements: <5 ms

Asynchronous Replication: Minimum 100 MbE or higher. The data link must be capable to transmit the replicated amount of data within the desired backup window

Hypervisor

Supported Windows Server version: 2012 or later

Storage

3 GB disk space reserved for installation and logging

The StarWind virtual disks must reside on the separate partition from the StarWind installation disk

Hardware RAID controller is highly recommended

Microsoft Storage Spaces is supported

Asynchronous Replication: The storage with replication journals on the primary server should have higher or equal write performance in comparison with the production storage array (on 100% sequential write with 8MB block size). The space reserved for the journal disk must exceed the amount of data written to the production storage array within the time frame between snapshots plus extra 25%

• Software RAID implementations are NOT supported. For recommended RAID settings, please, read the KB article.

IMPORTANT NOTE: Server with LSFS devices and Data Recovery (DR) server (in case of Asynchronous Replication) should fit the LSFS device requirements.

StarWind Virtual SAN (VSAN) for vSphere VSAN for vSphere

CPU

Minimum 4 virtual 1.7 GHz processors reserved

RAM

4GB
If using cache, an appropriate amount of RAM should be assigned

Network

Heartbeat failover strategy:
2x network interfaces (1xStarWind Synchronization and 1xiSCSI traffic/Heartbeat) + 1x network interface (Management/Heartbeat)
At least one Heartbeat interface must be on a separate network adapter and redundant

Node Majority failover strategy:
2x network interfaces (1xStarWind Synchronization and 1xiSCSI traffic) + 1x network interface (Management/Witness node)

Network Bandwidth

Synchronous Replication: Minimum 1 GbE or higher
Latency requirements: <5 ms

Hypervisor

Supported vSphere version: 5.5 or later

Storage

20 GB Virtual Disk reserved for OS. The StarWind virtual disks must reside on the separate partition from the StarWind installation disk

All Virtual Disks must be Thick Provision Eager Zeroed or the entire HBA/RAID controller must be passed through to the Virtual Machine

For recommended RAID settings, please, read the KB article.
3
Virtual Tape Library | VTL

Virtual Tape Library (VTL)

CPU

Minimum one 1.7 GHz processor

RAM

4GB

Network

1 NIC interface (VTL traffic) + 1 NIC (Management)

Network Bandwidth

Minimum 100 MbE or higher

Latency requirements: 100 ms or less

Hypervisor

Supported Windows Server version: 2012 or later

Storage

3 GB disk space reserved for installation and logging. The StarWind virtual disks must reside on the separate partition from StarWind installation disk

Supported Backup

Acronis Backup (10 – 12.5), ArcServe Backup (11.5 – 17), ArcServe UDP (5.x – 6.0), Bacula (9.2.0), Commvault (9.0 - 11), EMC AVAMAR (via ADMe) (6.1 – 7.5), EMC NetWorker (7.6 - 18.1), IBM TSM (6.2.2 – 8.1.5), HP DataProtector (7.x – 9.0), Microsoft DPM* (2012 - 2016), Unitrends (9.1 - 10), Veeam Backup & Replication (9.0 - 10.0), Veritas/Symantec BackupExec (12.x - 20.3), Veritas/Symantec NetBackup (6.x - 8.1.2), Quest NetVault Backup (12.4)

• Software RAID implementations are NOT supported. For recommended RAID settings, please, read the KB article.

IMPORTANT NOTE: In order to fit the ransomware resiliency, the VTL should be located on the dedicated storage/host which must be isolated from the production environment. Please read the following document for details: Backing up StarWind Virtual SAN Environment: Best Practice.
4
Management Console

Management Console

CPU

Minimum one 1 GHz processor

RAM

256MB

Network

1 NIC interface

Network Bandwidth

Minimum 100 MbE or higher

Supported OS

Server OS: Microsoft Windows Server 2008 R2; 2012; 2012 R2; 2016 Desktop OS: Windows 7; 8; 8.1; 10

Storage

256 МВ disk space reserved for installation and logging

IMPORTANT NOTE: Windows Server Core or Microsoft Hyper-V Server as a base OS is incompatible with the StarWind Management Console local installation. In this case, StarWind Management Console should be installed on any other computer. Please note that for remote management with default settings, port 3261 must be open.
Safe & Remote During COVID-19
StarWind VDI & Home Office