4GB
If using cache or Asynchronous Replication, an appropriate amount of RAM should be added
Network
2 NIC interfaces (StarWind Synchronization and Heartbeat/iSCSI traffic) + 1 NIC (Management) It is recommended to set jumbo frames (MTU) to 9000 for iSCSI and Synchronization traffic
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.
CPU
Minimum 4 virtual 1.7 GHz processors reserved
RAM
If using cache, an appropriate amount of RAM should be assigned
Network
2 NIC interfaces (StarWind Synchronization and Heartbeat/iSCSI traffic) + 1 NIC (Management)
It is recommended to set jumbo frames (MTU) to 9000 for iSCSI and Synchronization traffic
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.
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
• 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.
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.
