Thanks for sharing your diagram.
You can check your setup against
1. Traffic mixing.
iSCSI and Sync are teamed with management in a single Hyper-V switch.
2. no redundant communication
Make sure that NICs are redundant in the server. In other words, you need 2 or more physical network cards.
If direct connectivity is not possible, make sure that Switches that are used for communication are redundant in each location.
P.S. No need to use the Hyper-V switches for iSCSI and Synchronization if you use Windows-native StarWind Service.
Also, consider trialing and building a POC system with one of our techs https://www.starwindsoftware.com/v17-request-live-demo.
You can check your setup against
- System requirements https://www.starwindsoftware.com/system-requirements
- Best practices https://www.starwindsoftware.com/best-p ... practices/
1. Traffic mixing.
iSCSI and Sync are teamed with management in a single Hyper-V switch.
2. no redundant communication
Make sure that NICs are redundant in the server. In other words, you need 2 or more physical network cards.
If direct connectivity is not possible, make sure that Switches that are used for communication are redundant in each location.
P.S. No need to use the Hyper-V switches for iSCSI and Synchronization if you use Windows-native StarWind Service.
Also, consider trialing and building a POC system with one of our techs https://www.starwindsoftware.com/v17-request-live-demo.
Statistics: Posted by yaroslav (staff) — Tue Oct 08, 2024 4:34 pm