Hi,

We updated the policy settings for all connections from virtual hosts to the storage nodes to "Least Queue Depth" .
Do we need to update the policy settings from Storage Node A to Storage Node B too?

I already have the witness quorum disk attached to the compute nodes and verified as a witness from hyper-v cluster configuration and for the MPIO policy settings failover only.
is there any other witness configuration missing on the node side?

they are dedicated storage and they are separate from the cluster compute nodes.

The witness is to be connected only locally.

I have 2 compute nodes and 2 storage nodes. how do connect witness locally?

What hypervisor do you use? Microsoft HyperV I got your point, I will check the iSCSI initiator if the sessions are active or disconnected right? 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? Synchro...

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. How can this be checked? Yes, backups induce storage latencies and if storage is RAID5 out of HDDs, synchronization...

1. Check if all iSCSI paths are available. HA devices must be connected from both nodes. All sessions for HA devices are connected but I need to check during the timeout error. is this that should be checked? 2. StarWind VSAN 8.0.15260 installed an old version installed, we will plan for the upgrade...

Hi again,

It is RAID5 Configuration with Kingston SSD Mix-load. the VM's stop responding and is affecting the production.

Is there any settings that you recommend to change/update?

Hi all.

out of a sudden, we started receiving the below warning/error

command WRITE underlying device response time is longer than expected 11 sec

After restart, everything works fine.

what could be the issue?