Minimum one physical 1.7 GHz processor
4GB
If using cache or Asynchronous Replication, an appropriate amount of RAM should be added
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)
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
Supported Windows Server version: 2012 or later
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%
Minimum 4 virtual 1.7 GHz processors reserved
4GB
If using cache, an appropriate amount of RAM should be assigned
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)
Synchronous Replication: Minimum 1 GbE or higher
Latency requirements: <5 ms
Supported vSphere version: 5.5 or later
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
Minimum one 1.7 GHz processor
4GB
1 NIC interface (VTL traffic) + 1 NIC (Management)
Minimum 100 MbE or higher
Latency requirements: 100 ms or less
Supported Windows Server version: 2012 or later
3 GB disk space reserved for installation and logging. The StarWind virtual disks must reside on the separate partition from StarWind installation disk
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.6.2 – 8.1.5), HP DataProtector (7.x – 9.0), Microsoft DPM* (2012 - 2016), Unitrends (9.1 - 10), Veeam Backup & Replication (9.0 - 9.5), Veritas/Symantec BackupExec (12.x - 20.3), Veritas/Symantec NetBackup (6.x - 8.1.2), Quest NetVault Backup (12.4)
Minimum one 1 GHz processor
256MB
1 NIC interface
Minimum 100 MbE or higher
Server OS: Microsoft Windows Server 2008 R2; 2012; 2012 R2; 2016 Desktop OS: Windows 7; 8; 8.1; 10
256 МВ disk space reserved for installation and logging