May I ask how did you benchmark the physical storage? As far as I know, it is a bit complicated to simulate writes and reads directly on SSD drive. I think it’s just a matter of inbuilt cache which we cannot go around in doing so.

Hi Guillame, I will recommend you to double check if your synchronization NIC is not used by any third party software/applications. Also, it would be great to see your ISCSI configuration as well. Which MPIO policy do you use? Looks like in your case it may be better to utilize "Failover-only&q...

I would say - that's not the best idea to use nested configurations, especially, in SAN - oriented scenarios even for testing purposes

Not sure if it's a good idea to test PoC with free version. Why it wouldn't be better to use a trial?

Hello, I've already noticed such behavior using other ISCSI server providers. Not sure if it's starwind related issue, looks more like ISCSI protocol limitation. However, it's never been critical for me. There is no impact in performance at all, so I don't see anything you have to worry about. In ad...

1. It could occur due to different reasons, malfunction or software issues, etc. One of the most common reason may be isAlive function performing. You can try to check Windows App event logs - there should be plenty of info to analyze. Here is Starwind KB article, explaining why full sync could happ...

Hi,

You are absolutely correct. Huge amount of questions about iSCSI restriction. Be attentive with sys requirements

I have serious doubts regarding the amount of IOPS you got without SW and cluster. Don't you mind that? Really poor performance for such device as, normally, PCIe SSDs should break 300k IOPS threshold on random reads. I really advise you to check your SSD configuration. Double check where it's being...

Looking through your questions I've found some bothering me as well. But, does LSFS-oriented approach is so crucial for you? Are you totally ready to go with overprovisioning restrictions? I ain't refusing all LSFS advantages and, obviously, it has excellent perspectives, however, regular image file...

Going with Windows Server 2008 R2 won't allow you to build Scale-out File Server, just because of it only supports SMB 2.0, while SMB 3.0 is required for this purpose. Your certainly can create shared file storage with SMB 2.0, however it won't failover. All these constraints confuse me, occasionall...

You've made proper conclusions. Free version isn't intended to use in production scenarios, actually. So if u wanna to get mirror between 2 nodes, and don't wanna rebuild (it's meant "to move to Windows Server 2012") your working environment, then will buy the commercial version, which is ...

Hi again

Switching to round-robin multi-path policy indeed can speed up failover and enhance performance generally. However, configuring the automatic storage rescan impacts just on availability of the storage once one of the Starwind VSAN nodes has crashed.

Hi

Have you configured all parameters of automatic storage rescan correctly from this guide? I would advice you to check them/

Dude, I guess something wrong with your iSCSI connections! perhaps, it sounds like i'm captain obvious, but still check them settings.

what\s version of starwind release are u using?