StarWind Software

During testing, I have powered off all devices, storage nodes, xen server compute nodes and switches to simulate a catastrophic power loss.

Current configuration is with 2 node starwind cluster, 2 dedicated 10G sync, 2 dedicated 10G iscsi, 1 dedicated 1G heartbeat and 1 dedicated management port.

After power is restored, the starwind nodes begin re-sync as expected, however the xen server devices are unable to connect to the starwind iscsi devices until a full synchronization has been completed.

I would expect that the node which is being synchronized from would be accessible to the xen server pool, however none of the paths are available.

Another issue I am seeing is during initial synchronization when I created the cluster synchronized at 10-12 Gbps, while the current resync is only syncing at 1 Gbps.

After booting, the xen server node appears to be attempting to connect to the starwind node that is not ready.

Any ideas how I can get xenserver to us one of the nodes while the second is synchronizing. As it is now, it appears to take several hours for the nodes to re-sync and during that time none of the vm's can boot.

I would expect that the node which is being synchronized from would be accessible to the xen server pool, however none of the paths are available.

This is the exact behavior offered. Which StarWind build do you use that you have issues with?
Post the output of from Xen Server nodes before simulating disaster and after.

I will need to send the the results after second volume re-synchronizes.

but before it does, I can say the output of multipath -ll is blank. But immediately after reboot, it is not. I have attached a screenshot of the xen server node looks like after a reboot.

I am using an older version of starwind. You and I worked with an issue where the newer install would not create the second sync or iscsi interface via powershell. I have tested with newer versions but it has been a few months.

Currently running 8.0.0.11456

The output of multipath -ll changes.. first it shows one storage repo, then the second, finally they all go away and results are empty.

Node is back up and running. Below is the good multipath -ll output

zendzipr,

Submit a ticket referring to this thread. I will keep posting any solutions here after we find out what is wrong there.

Boris,

Thank you. Request submitted. Ticket number is 56702

Great. Keeping our communication there for now, with the final solution to be posted here later.

During a remote session with zendzipr we were unable to reproduce the issue he had encountered earlier. StarWind VSAN worked as expected and provided the Xen Servers with access to storage with only one partner node of the HA setup being synchronized.