StarWind Virtual SAN

通過在管理程序服務器之間簡單地鏡像內部硬盤和閃存，從而消除了對物理共享存儲的任何需求。它通過利用相同工作負載的硬體資源來降低虛擬化開支（資本和運營）。憑藉獨特的StarWind開發的技術，StarWind VSAN 以簡約資源保持高性能和數據高可用性。StarWind Virtual SAN使用商用現成硬體提供了性能和可靠性，無需昂貴的專有組件。

StarWind Virtual SAN比其他軟體定義存儲平台簡單，價格低廉，性能更高，功能更多。StarWind VSAN只需兩個節點即可進行簡單的基本配置，無需投票或仲裁設施，操作非常簡單。它降低了需要較少硬體的成本：沒有交換機，沒有強制閃存，沒有10GbE和更少的服務器。StarWind VSAN只需要兩個許可節點即可根據需要處理多個節點的基礎架構。基本配置支持許多類似解決方案中不可用的功能，例如異步複製，線內和脫機重複數據刪除，日誌結構化，多層RAM和閃存緩存。

StarWind VSAN支持融合場景，也可以在現有虛擬機管理程序服務器之上進行超融合。它運行在便宜的商用現成硬體上，不會造成硬體鎖定。許可證是永久的，因此它們永遠不會過期並導致更新的額外費用。與單一用途的開放源代碼免費軟件不同，StarWind VSAN使用內部開發的代碼，在全球範圍內已得到充分驗證，並且是原生Windows應用程序，無需任何定制的Linux / FreeBSD分支。StarWind VSAN受StarWind支持，並且還可以使用Microsoft和VMware支持服務。StarWind Virtual SAN與競爭對手的完全區別可以在這裡找到。
 

優點

特別簡單
StarWind Virtual SAN作為本機虛擬機管理程序組件或虛擬機運行，並且不需要任何深層存儲和網絡管理或UNIX管理技能。在Hyper-V，VMware或Windows中經驗最少的典型系統管理員可以安裝，配置和維護VSAN操作。

成本效益
StarWind Virtual SAN將成本降低至少一半，這意味著運營和資本支出。它消除了實際的物理共享存儲，相應的基礎架構，相關的部署和維護活動。StarWind VSAN適用於商品硬體，因此不僅購買和維護的硬體更少，而且所需的硬體價格低廉。

性能和功能
性能不受簡約硬體足蹟的影響，降低了部署和管理成本。StarWind Virtual SAN帶來了服務器端閃存和內存緩存，日誌架構和絕對簡約的I / O路徑。由此產生的性能無論是典型的虛擬設備還是物理共享存儲都無法匹敵。

系統需求

StarWind Virtual SAN (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%

StarWind Virtual SAN (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