Hi Constantin,
well I did nothing to provoke it, as it is a production environment. It happened when the switch died. So you are right assuming the network connectivities got lost.
As we sorted that one out, I've got one more question.
As Starwind is running on top of windows, reboots are inevitable (e.g. when patching the OS). Is it better to stop the service before the reboot or doesn't that matter? I'm afraid that the service might be terminated ungracefully by windows if it takes too long to terminate.
In the long run, I'll avoid those reboots completely by adding another Storageworks x510 replacing the current server that has some other services running and thus needs to be patched. The x510 is a nice device to be used with Starwind if you disable the windows home server functions and the smb protocol and close all ports but 3389 and 326x
The performance is outstanding and you can use the built in raid functionality of windows for mirroring. In addition with Starwind HA this makes a very reliable iSCSI target for my vSphere-Cluster (unless the switch dies
)
Do you know devices that are like the x510, but with more than one nic?
cu
Volker