I've seen your suggestion of delaying the starting of the initiator service, and I don't like much, it doesn't seem very clean. Also I'm not 100% sure this problem is caused by the local target being up late as you suggest. For example, I've turned off node 2, caused a hell of a lot of write activit...

And what would happen if I set Round Robin (with subset) and somehow Starwind target reports the loopback path as optimized ? Would that work? That would be ALUA. That way windows would prefer the loopback even if that path comes up late. I'm using just 1gb NIC, so I'm trying to avoid writing to the...

manually?? Seriously?

This is still happening with Windows Server 2016. I know it does not seem a StarWind problem, but there's gotta be some logic or explanation as why Windows is changings Paths IDs on reboot. I can't figure out its logic. Sometimes it seems it leaves all as it is, sometimes it seems changes active pat...

Law is simple: One node -> Write-Thru, many nodes -> Write-Back. Let me see if I get this write-back cache policy right. Let's suppose 2 node hyperconverged scenario. I'm kind of afraid of blackouts in combination with write-back policy. You are saying no matter if write back cache is enabled or mu...

Similar problem here. Hyperconverged 2 nodes FCI SQL cluster. Windows Server 2016, SQL 2016. Using latest version 8.10695 I've configured all MPIO paths correctly as per Star Wind Best Practices, Fail Over Only, 127.0.0.1 Active , other iSCSI subnet standby. After a grecefully node reboot, al MPIO p...