Never faced such a strange behavior. Normally such kind of device should perform 5-10% slower than a local one.

Try to connect additional iSCSI sessions (like connecting 2-4 times over loopback). I noticed that sometimes an internal iSCSI limitation could lead to such performance discrepancy.

Ok, gotcha.

Basically, I did not have any troubles with standalone LSFS almost for a year already.

Hi, Jhamm.

FYI some thoughts regarding L2 also:
https://forums.starwindsoftware.com/vie ... f=5&t=4390

Hi, Gorb. Pretty nice and reasonable plan. Only a few thoughts from me: I believe it is not possible to enable L2 cache in write-back mode anymore. Only write-through improving reads. Furthermore, I noticed some strange performance problems with L2 cache on traditional SSD drives. Read performance w...

Hi, Hste.

Do you have HA LSFS devices or standalone ones?

VSA installer (and OVF template) never worked for me. Always did the things manually.

The manual way is sometimes the best way :) Did the job multiple times for me so far. Just create a new VM and install Windows inside it. Then download the latest StarWind build from the website and install it into newly created VM. Provision some physical storage as VMDK into VM and configure it fo...

Nope

I am downloading it already
Current (V8) build is 8716 (6 November 2015)

Yeah, all of us here heard that already... https://forums.starwindsoftware.com/vie ... =30#p24707

... over a month ago

Hi McGuffin, Such a difference is very weird. Especially for LSFS devices. Have you tested it locally on SAN like just connecting starwinds iscsi targets over 127.0.0.1 with a couple of sessions and setting HDTune or IOMeter on it? Just to ensure it is not network :) And yeah... LSFS device size, L1...

Hi, mate. I've got LSFS up and running in two different locations: 1) Standalone LSFS device with deduplication. No caching, since the server where StarWind runs is an old HP ProLiant box having little RAM in it. Just for backup and file sharing purposes. I am happy with how it works and dedupes. 2)...

Sure, Elvis.

Have fun testing

Hi mate!

Have you tried to go to iSCSI initiator settings and point to properties and device options there? There is an MPIO policy selection box, so you can define whether round robin or failover only is used for each device.

Yeah, it is.

Since I have multiple customers using StarWind in their environment, I often face the "Invalid Partner info" problem. A solution that always worked for me was to check whether DNS names of both hosts participating in StarWind HA replication resolving correctly. The fastest way to ensure th...