Here's the log from test server with 13279 build installed: https://drive.google.com/open?id=1nHvhpNo26GVtQfj_9nXse3htMRdYgKJL Also some older logs from our production server with previous 13182 build: https://drive.google.com/open?id=18aWRB6Xqr4cXq4WKGPv6rPozsQMg1EQg For now our production servers ...

Looks like the problem still exist in the new build 13279.
Are you going to fix it someday?

Hello, guys. Could you explain what's the point of connecting witness targets only through the loopback address? And what exact behavior should we expect during fail over? I've run a few tests and had some bad results. Not sure if I've done everything correct, so please could you have a look? Here's...

Already did that. Previous build 12767 run perfectly since the release, so I've installed it and have my fingers crossed.
Is it a new feature or just a bug with license expiration check?
Or gentle reminder for us to actually buy your great product?

Hello again, another crash happened today. Same reason - license expired, all storage is down.
What's happening guys? Our license just suddenly broke or it has something to do with the new build?
Because for more than 2 years since we using vSAN there was no problem at all!

Hi, we had a serious crush today, because of license expiration too. We've been using Starwind vSAN free license for a long time without any problems. But this evening all connections with iSCSI targets were lost and our Hyper-V cluster was shut down. I checked the logs and found possible cause mayb...

Now I get it, thank you, Sergey! That's what I needed to know.

Here's been a discussion about performance so I'd like to post another question. What actual performance boost should I expect with LSFS-device based on this hardware? 5 x 2TB SATA HDD's, 5400RPM, 4k, RAID 5 IBM ServerRAID M5120 RAM L1 Cache: 1GB RAM Deduplication cache: 4GB Logical block size: 512 ...

No, nodes weren't stopped at the same time. In my first post I wrote that Host 2 shut down itself first and only after that Host 1 was stopped. Right before Host 1 began to shutdown I verified that all devices on it have been synchronized. So I've expected that after I restart it again they would ke...

I've read the article, thank you. So in the case when I know for sure which host has been shut down first and last I could use automatic synchronization simply by turning hosts online one by one. And then they will synchronize according to their priorities, right? I was a bit puzzled to see all devi...

Hello! I'm trying to implement correct shutdown procedure for my Hyper-V cluster in case of power outage. We have Host 1 and Host 2 with Starwind vSAN (free version) installed on them. Both connected to the UPS1 and UPS2 (Smart-UPS SUA1500) in redundant fashion. Heartbeat and synchronization channel...

Has been that issue with ODX support fixed in the current build 11156 ?

I've attached diskspd results. As you can see the performance between local storage and Starwind device placed on it is nearly equal. Only sequential operations with 4k block size have strange degradation. If Starwind synchronization works with 64k blocks and Hyper-V also using it. I wonder, is it a...

By the way, how can we use this nice script "CreateHA(two nodes).ps1" in case of partner node total failure? For example, I'd like to synchronize survived node with new server? I've tried to use Add-HADevice with -initMethod "SyncFromFirst", but it's only create a new image file ...

Ivan (staff) wrote:Synchronization channel - technically it will work, but I would like to notice that in such configuration 10 Gbps could be not fully utilized

Of course you right! In that case maximum bandwidth I'll get would be the slowest one. Excuse me, I totally forgot about it.