I think I worked out what was happening, Boris, so I won't log a case. A previous test failure must have caused the Starwind devices to initiate a full sync (which I did not realise was running). On testing later while the sync was still running, attempting to put the devices in maintenance mode com...

I do. You can see in my post above, where I include the application log that MM is noted as being rolled back, just after heartbeat links all fail.

Observations are that a full sync is occurring after boot of both nodes because the maintenance mode (which had been set successfully according to logs) is being rolled back just prior to power-off for some reason. I can not see an obvious reason for that roll-back. Could it be related to sending th...

Did the script work as expected for you? Actually, Something is not quite right with the Starwind bit. I have gotten my scripts to the point of everything seeming to work, but on re-start the second node (never seen the first do this) shows that it is re-synchronising, and takes quite a while. PS C...

...have a look at https://www.starwindsoftware.com/resource-library/starwind-virtual-san-gentle-shutdown-with-powerchute ... Great script, and Starwind works perfectly with maintenance mode. As for Hyper-V failover clusters and their behaviour when you're not using SCVMM and its maintenance mode, n...

From 11818 on, StarWind VSAN has got Maintenance Mode for the HA devices... You're a good man to point that out. It will be implemented today! :D Could the slow sync be due to the small number of processor cores in my set up, hence worker threads? Would it be ill-advisable to mess with those settin...

What was the outcome upgrading from v6 to v8? Curious as I'm on v8 latest and am seeing the exact same thing in terms of full sync performance. Drives me nuts every controlled power outage (or UPS test) where both nodes are shut down, hence full sync time. I've twin 10Gbps links, and each are only d...