As far as I know there is no changes in LSFS architecture.
And in release notes there is nothing about LSFS.
I hope there will be some changes, but they are not in this build.

Generally, your synchronization channel bandwidth should be equal to iSCSI channel(client connections). But 1GbE LAN is not enough for Sync/iSCSI channels. So you need to use few 1GbE cards for a Sync/iSCSI channels. For iSCSI channel you can use your two switches. For Synchronization channel would ...

In case of Hyper-V hyper-converged scenario you should install one domain controller(primary) directly on Windows. But for fault tolerance you need second domain controller(secondary). For secondary domain controller you need to create VM and install DC(secondary) directly into VM. You will have two...

Hi, First of all I would take a first look on a few documents: https://www.starwindsoftware.com/technical_papers/getting-started.pdf And if you want to use Virtual SAN, here is the Hyper-V separated: https://www.starwindsoftware.com/technical_papers/starwind-virtual-san-compute-and-storage-separated...

Hi Epnk, It`s strange behavior for V2V from my experience. As far as I know, there is only one chekbox before converting, and it`s windows repair mode. And repair mode allows you to adapt OS to the new hardware. As we can read from the whitepaper: StarWind V2V Converter allows for the conversion of ...

Yes, you quite right. You can migrate all your present VM`s into second node, configure first node, create on the first node few Starwind Image files. Connect them into ESXi, create datastore. Migrate everything on the first Image file, on the first node. Configure second ESXi node. Create HA from y...

In case of Hyper-Converged scenario, you create two VM`s, add Eager Zero datastores based on your physical disks(each VM should me the same) Install Starwind on your VM`s Create devices based on previously added Eager Zero datastores After you connect those devices into your ESXi and create datastor...

With Starwind free you can`t install Starwind inside VM`s. In case of Hyper-converged scenario Starwind VM`s are working with local storage. Synchronization between Vm`s are using direct connections between your ESXi, you need to add those NIC`s into ESXi after add into VM. Off course, local storage...

Main difference is that you can install Starwind into VM`s and use full High Availability features.
More about difference, you can find here:
https://www.starwindsoftware.com/whitep ... s-paid.pdf

Hi For now in free license iSCSI connections are restricted for hyper-converged scenario. But as far as I know you can ask for NFR license(if it`s not production usage) here: https://www.starwindsoftware.com/starwind-nfr-license-users According to best practices you should use 10GBE NIC`s on sync ch...

Hello
Could you please try to use the function "VMware growable image"
It may help.

Hi
About difference between free and paid version you can find here: https://www.starwindsoftware.com/whitep ... s-paid.pdf
I hope it will help.

Hello
As far as I understood you, you want to configure RAID stripe size.
As I`ve heard better stripe size for RAID 5 is 64K.
I have almost the same configuration in my test lab with 64K stripe size and it works well.

Hi
Adding L2 cache only available with device recreation.
In case of HA you can make it without bringing down, by creating devices one by one.
But in case of standalone flat device be down time required.

Hi

As far as I know, in case of SSD RAID with L2 cache failure starwind devices will fall down.
And about path, you can change it only if you recreate device.
I hope it was helpful.