Hi Tom, Yes, we have not included automatic re-synchronization between the nodes alowing administrator to decide what way to synchronize the cluster. Fast sync is an incremental synchronization that only synchronizes the data that was actually changed while one of the nodes was down. So, fast sync i...
What I could suggest is try installing Spotlight by Quest Software on both Pcs - it's quite an intuitive piece of software that will give you the clues to the bottlenecks.
What you can do from the StarWind point of view is to "bind" it to listen to a specific network interface. What you are saying totally makes sence in terms of dedicating a separate network and storage segment to iSCSI. Moreover, Vmware recommend doing that for iSCSI SANs. To "bind&quo...
We get the same in our testing lab actually, but that is related to a VMFS (as well as other clustered file systems that you format the images with). It for some reason creates a large overhead, not sure why. In this case the only recommendation would be to create larger image files.
You are right when saying that there is really a lot of users that don't experience any crashes while using StarWind. The service can really work for months and months without a single failure. I will follow-up with Bob on the status of your issues so that we could get this resolved.
Are there any Windows updates that make StarWind PC reboot? Also, is there 1 NIC interface only to the StarWind PC, or are there several ones (MPIO enabled)?
Toni, When you create a device using StarPort, do you select "Local iSCSI device" or "Remote iSCSI device"? Also, does your card display any error messages or any other types of warnings, or is it just not able to see the target created by StarPort? MS iSCSI Initiator does actual...