Wanted to provide an update in case anyone else runs into this issue. I noticed one of the HA starwind files on the second node didn't quite match (sector size was different). I checked they all matched, and everything else matched perfectly. I also adjusted the sync priority to 5%, although I suspe...

If tou have SSD cache in place, it could be the culprit. Hello, Apologies, I just checked and I don't see cache enabled on any of the disks (at least not in Starwind). I did increase the thresholds per your recommendation on both nodes. I also set the sync priority to 5% on both nodes, just to vali...

There are storage hiccups. Here is what I see on host2. For example 12/18 12:49:39.016942 21f4 IMG: ImageFile_IoCompleted: Warning(Time FileIO): request(0x0000023EDCEFD470) ssc(0x0000023EDE4B6E10) function(Execute SCSI Command) opCode(0x8A), timeFileIO = 14765 ms, g_cmdExecTimeWarningLimitInSec = 3...

Hello,

Replication was set to 5%. I also let it attempt a full sync a few times. I'm still seeing the same issue.

Host 01 logs: https://mega.nz/file/iIM1AYzb#fmNW9e-Ct ... QCALHWymAw
Host 02 logs: https://mega.nz/file/OZFUECab#5IBNZz6Hw ... Ocd6oPXBqc

Thanks for your update. 870 and 860 are consumer-grade SSDs. Update to 20086, and reduce replication priority (stop service on the node that undergoes synchronization> edit the header under /headers > set 50 to 5). Please also see what is going on with the storage (hearing more about the configurat...

Oh, as a side note. 20084 is not that stable when it comes to handling unmap (see https://www.starwindsoftware.com/release-notes-build) if that's applicable to your storage. Please update at some point. Also, could you please share info about the underlying storage (disk type, RAID, caching)? The d...

When I add a host in Starwind, I have the option to import an existing device. From there, I can configure the replication to the HA partner. That is what I am referring to. As long as that remains intact, the "data" will remain.

Hi,

Yes that is fine. The local disk should be available shortly after if I am importing an existing disk, correct?

Hello,

I did stop it on both. I was going to try to recreate everything again. I assume as long as I don't delete the .img on the host with the correct data I'll be able to import an existing image after I delete all headers and all config on both nodes?

Hello, I've removed the vSwitches and configured the IPs directly on the NICs. I've also lowered the sync priority to 50% as you requested. Datastore03 isn't in use currently, but this isn't something that just affected the disk replicated through that. It is affecting all replicated devices. I'm ru...

Hi, Yes, each physical NIC is set to a vSwitch (Sync and iSCSI). The vSwitch is then assigned the IP. vSwitch_01 and vSwitch_02 are used for VM traffic and heartbeats, it isn't directly related to replication or iSCSI. Here is a Mega link to the latest log files: Host 01: https://mega.nz/file/DR1R2D...

Hello,

These are Hyper-V hosts, running Windows Server 2022 Datacenter. Starwind vSAN is running as a windows service on them.

Hello,

These servers are directly connected via 25G NICs. 1 is used for iSCSI, the other is used for Sync.

I can't post the full log, the forums don't seem to allow me to. But here are the logs for the last day from Host01. https://pastebin.com/CPTBAxk4

Hello,

Do you mean delete the .img files on Host02 and the applicable headers? If so, I did that when I reimaged Host02 and established a fresh sync.