StarWind Software

Hi, we've had a mostly successful test of the vsan product providing HA storage to hyper-v using the hyper-v hosts themselves to provide starwinds replicated storage.
We also have some virtual hosts that export physical iSCSI targets for backup purposes.

Is there any limitation that would prevent starwinds free produce exporting such a standalone, non-replicated target?

The configuration process appears sane and completes OK - everything looks like it would work. Offline the physical disk in the target host OS, create a target config in starwinds OK

Discovery is successful, but when initiator attempt to connect it reports service unavailable and the target host logs an event along the lines of a read-only warning (regardless of how the local device is configured in the host OS) - unfortunately I don't have the exact error log immediately on hand.

Is there any feature limitations that would prevent a physical, standalone ISCSI target being exported. the replicated vSAN appears to be fully functional.

Current testing suggests the standalone target config works fine as a standalone config, but on initial testing the standalone target could not be connected to exported from a host also exporting vsan...

Any suggests, am I not being clear enough?

There are no limitations for the standalone target.
Please check if port 3260 is not in use and all networks are accessible.

Thanks I'll look for a configuration error. As mentioned, 3260 is obviously open because it's exporting a vsan. It was only when attempting to add a standalone target to that config that the standalone target failed - discoverable but attempted connection from initiator returned "service not available". Unexpected inheritence of a CHAP config pops to mind if there are no limitations...there was no explicit CHAP config in the test config. A read-only type event log was logged on the target host on attempted initiator connect.

Have you got any update on this to share?