We are really sorry about the delay in releasing new build. Right now it's at the final stage of testing.

darklight, thank you for sharing your knowledge with others

Michael, do you have any questions?

Thank you for your help, darklight.

vsan2015, do you still experience this issue after updating to the recent StarWind build?

Thank you for your help, darklight.

plastilin, do you have any questions?

Thanks for your help Rajesh and darklight.

D9BDCEA2CE, do you have any questions?

Thank you for your help, darklight.

Vincenzo, do you have any questions?

Thank you for helping out, darklight

Is there anything else we can help you with, Dave?

We have finished the script. In order to manually flush cache of your StarWind device, you should do the following: - Download FlushCache.ps1 file attached. - Open file with Wordpad / Notepad ++. - Change $deviceName="imagefile1" value to correspond the name of your StarWind device. - Save...

I believe that it's possible, but requires some creativity and applying of a weird workaround. For example, look toward a nested virtualization (ESX inside Hyper-V and so on)

And also it's better to ask VMware about its vmfs5.

If it possible, then yes, it is a good choice. StarWind knows all SSD specific commands like TRIM and successfully deals with them.

Thanks Delo123

frufru,

It is up to you. I believe that PCIe SSDs are faster in most cases. My choice would be PCIe SSD.

Ok, 2 10 Gbps NICs are fast enough if storage is slower. BUT there is another concern - VLANs (sync and iSCSI assigned to the same physical NIC) may cause instability, at least, it was confirmed a few times by our techs. Therefore, you are welcome to use VLANs, but in this case FailoverOnly is the o...

Hi Dave, RoundRobin is a good choice if sync channel is extremely fast or at least faster then storage where image files are located. RR policy carefully balances workload between to servers. If sync channel is not super fast, then FailoverOnly is definitely the choice! Because this policy excludes ...

Hi, First of all I'd like you to follow StarWind release notes here https://www.starwindsoftware.com/release-notes-build and here https://forums.starwindsoftware.com/viewtopic.php?f=5&t=2069 In you case, it might be a performance improvement, but nevertheless it requires testing. For example, we...

YEES! We will include it in StarWind best practices since 512b image block size on top of Storage Spaces may cause such weird issues.

Thanks for the update.