Intel Xeon E5620 (or higher) or equivalent AMD Opteron
The minimum recommended CPU is Intel Xeon E5620 or equivalent. Intel Xeon X5660 or equivalent can be used in order to maximize the performance.
4GB is the minimum RAM amount that should be installed on a server that is running StarWind Virtual SAN. In case of implementing StarWind High Speed caching, an appropriate RAM amount should be installed additionally. The cache-dedicated RAM amount should be equal to or higher than the one reserved for iSCSI targets caching.
In-line deduplication with LSFS requires 7.6 GB of RAM per 1 TB of deduplicated storage.
IMPORTANT NOTICE: Always reserve at least 4 GB RAM for Windows internal processes and the StarWind Virtual SAN engine.
- Hardware RAID controller is highly recommended
- StarWind Virtual SAN supports Microsoft Storage Spaces
- Software RAID implementations are NOT supported
Depending on the storage requirements, the most appropriate RAID configuration can be selected. StarWind recommendations for the proper HA storage design are:
- RAID 10 for SAS or SATA hard drives
- RAID 1, 5, 6, 10 for SAS or SATA SSDs
RAID 5, 6, 50, 60 can be considered for a backup/VTL environment with mostly sequential workloads, where the best write performance is not a critical requirement and the main goal is to achieve the maximum storage efficiency. In order to receive an additional information regarding the particular storage design, please contact StarWind Support.
The minimum requirement for StarWind installation and logging is 3 GB of disk space. The StarWind virtual disks must reside on the separate partition from StarWind installation.
Minimum of 2 x 1GbE physical NICs
The minimum supported bandwidth is 1 GbE. In case of an intensive workload, the scaling to the 10 GbE or 40 GbE infrastructure should be considered. In order to maximize the SAN environment performance, it is highly recommended to use 9K Jumbo frame capable network equipment.
StarWind Synchronization network has a prerequisite of both NIC (preferred) and switch (if used) fault tolerance measures. The use of STP (Shielded twisted pair) CAT6 (or higher) cable is required for the Synchronization Network for both crossover and server-switch connections.
Network latency requirements
Maximum Synchronization network latency should not exceed 5 ms.
Network latency higher than 5 ms may lead to the HA performance degradation.
It is recommended to consult on long-distance cross-datacenter deployments with StarWind Technical Engineers on a per-case basis.
Supported Operating Systems
- Microsoft Windows Server 2008 R2 (partial support)
- Microsoft Windows Server 2012
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2016
Supported Microsoft Windows Server GUI-less editions
- Windows Server Core 2008 R2 (partial support)
- Windows Server Core 2012
- Windows Server Core 2012 R2
- Hyper-V Server 2008 R2 (partial support)
- Hyper-V Server 2012
- Hyper-V Server 2012 R2
- Hyper-V Server 2016
IMPORTANT NOTICE: The use of Windows Server Core or Microsoft Hyper-V Server as a base OS is incompatible with StarWind Management Console local installation. In this case, StarWind Management Console should be installed on any other computer. Please note that for a remote management, port 3261 has to be open on both machines’ firewalls.
Microsoft Windows Desktop editions compatible with StarWind Management Console
- Windows 7
- Windows 8
- Windows 8.1
- Windows 10
System requirements for deploying StarWind as a virtual machine:
CPU: 4 virtual processors with 2 GHz reserved is the minimum requirement to ensure the proper functioning of VSA.
Network Settings: 2 NIC ports dedicated as separate virtual switches is the minimum requirement for StarWind synchronization and iSCSI traffic. The recommended minimum bandwidth is 1 GbE. In case of an intensive workload, the scaling to a 10 GbE or higher should be considered.
Infrastructure: Supported vSphere version: 5.x and later.
IMPORTANT NOTICE: When using StarWind with synchronous replication feature inside of a virtual machine, it is recommended not to make backups and snapshots of the virtual machine with StarWind Service which could pause the StarWind virtual machine.
Pausing the virtual machines while the StarWind service is under load may lead to split-brain issues in devices with synchronous replication and data corruption.
For specific recommendations, please contact StarWind Support
RAM: For storage workload handling, the primary storage system must allocate 128 MB of RAM additionally. The disaster recovery location must correspond the LSFS device requirements specified here: https://www.starwindsoftware.com/resource-library/lsfs-container-technical-description
IMPORTANT NOTICE: The requirement is applied only to StarWind-related RAM expenses. The memory for OS, hypervisor, and other applications should be sized separately.
Bandwidth. The minimum required throughput is 10 Mbps. It is recommended to use the data link that is physically capable of transmitting the replicated amount of data within the desired backup window time.
Physical Storage Considerations: The performance of the drive storing the primary node replication journal must be higher or equal to the maximum write throughput of the production storage array. The measurement should be held under “8MB block size 100% sequential write” pattern. The reserved free space of the journal disk must exceed the amount of data written to the production storage array within the time frame between the snapshots, plus an additional 25%.
The disaster recovery location must correspond the LSFS device requirements specified here: https://www.starwindsoftware.com/resource-library/lsfs-container-technical-description