Storage Sync for Hyper-V has been certified to work on the following host operating systems.
- Windows Server 2012 (Storage Sync 11.x)
- Windows Server 2012 R2 (Storage Sync 11.x)
- Windows Server 2016 (Storage Sync 11.x and 12.x)
- Windows Server 2019 (Storage Sync 11.x and 12.x)
Hyper-V role on Windows is supported only on x86-64 variants of Windows. We recommend using the newest version of Storage Sync.
System Requirements for Enabling Hyper-V Role
Please refer to the Microsoft documentation on virtualization here.
Memory and CPU
We have tested and certified Storage Sync for Hyper-V on systems with Intel processor cores. For more information about optimizing the performance of your host platform for Hyper-V, please click here.
We recommend that you allocate 4GB RAM and 2 processor cores for Storage Sync for Hyper-V.
Microsoft recommends users install multiple Network Interface Cards (NIC) on the Hyper-V host machine. Microsoft also recommends that you associate your Hyper-V with a dedicated physical NIC card.
Microsoft has suggested that Hyper-V users disable TCP offloading for the Hyper-V VM’s associated NIC card to enhance Hyper-V network performance, but we recommend that you consult with Microsoft Support before making such changes.
There is a maximum storage of 16TB per each instance of Storage Sync. Storage can be allocated in increments of 1.8TB up to the 16TB limit. We recommend deploying multiple Storage Sync VMs if you need to access more than 16TB of storage at a specific office location.
|Storage Sync Performance Categories||Limits|
|Maximum Number of Mapped Users||2000|
|Maximum Number of Files and Folders on Local Disk||10 Million|
|Maximum Number of Concurrent Users Accessing the Network Drive||200|
These figures are approximations; sync times can vary greatly depending on factors like file size. For assistance with configuration of the Storage Sync device, please contact a Professional Services representative.
Update Anti-Virus Exclusion List
Some anti-virus software applications (such as TrendMicro AV and Forefront) prevent the deployment of virtual machines as part of their default security settings. Please configure your Windows host's anti-virus software to exclude “VHD” and “XML” file types. Click here to learn more about the effects of anti-virus software on a Hyper-V configuration.
Best Practices for Physical Servers Hosting Hyper-V
This technical article provides best practices for enabling the Microsoft Hyper-V role on Windows Server.