The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
When timeout, please see if storage is connected from the synchronized server. There might be misconfiguration as synchronization drop on one node should not affect production uptime.All sessions for HA devices are connected but I need to check during the timeout error. is this that should be checked?
Yes, backups induce storage latencies and if storage is RAID5 out of HDDs, synchronization drops might be frequent.a scheduled backup job is running hourly using a third-party application for the VMs. does this matter?
Are disks HDD? If HDD, this is not recommended config, and Synchronization drops might be common.Hardware is healthy but using an old HPE DL380e Gen8 / P420i RAID Controller with RAID5 configuration.
How can this be checked?When timeout, please see if storage is connected from the synchronized server. There might be misconfiguration as synchronization drop on one node should not affect production uptime.
NotedYes, backups induce storage latencies and if storage is RAID5 out of HDDs, synchronization drops might be frequent.
Mixload SSDs installed in this setup.Are disks HDD? If HDD, this is not recommended config, and Synchronization drops might be common.
You can check it in the iSCSI Initiator. What hypervisor do you use?How can this be checked?
Microsoft HyperVWhat hypervisor do you use?
Synchronous Replication
Fixed an issue with synchronization/heartbeat channels unable to restore the connection when performance degradation occurs on the underline storage and VAAI is enabled for StarWind HA Devices.
VAAI/CAW is relevant to vSphere only.By the way, I was reading the release notes of the latest version of Starwind and I see the below fix. does this relate to the sync and HA error?