We have this feature in plans, but it is not ready yet.

Yes, we have plans to start developing in the next year.

SATA SAS This is worst case scenario (no L1 cache, no L2 cache).

After update it should be: <options> … <!-- <iScsiDiscoveryListInterfaces value="1"/>--> … <LocalizationDir value="Localizations"/> <iScsiDiscoveryListInterfaces value="1"/> <DefaultStoragePoolPath value="My Computer\D\img\"/> </options> In other words the com...

I've just upgraded to build 7185 from 6884 and this bug is still present, i.e. after upgrade the CFG file changed from: <iScsiDiscoveryListInterfaces value="1"/> to: <!-- <iScsiDiscoveryListInterfaces value="1"/>--> Now interestingly, the existing iSCSI initiators have reconnect...

Blue407 wrote:Wireshark log

please e-mail it directly to beta-testing@ or support@

Thank you.
But I don't see the attachment...

Hi, please follow these steps to help us find what's wrong: 1) What tape library and SCSI/SAS controller do you use? 2) On StarWind (Tape Redirector) machine install and launch wireshark, set packet filter options ("tcp port 3260" if you are using StarWind v8 software, or "tcp port 33...

Please zip and send us starwind logs to check what's wrong.

We'll re-check that. Thanks!

The idea of cluster is to simplify the future devices creation process.
So it uses the default storage pool path to save virtual disks there and default network settings (sync, heartbeat) which you specify when add server to the cluster.

the screenshot was just of the ha option greyed out for ramdisk. Alex said you can't put a ramdisk into an ha sync... well, poking around in the gui, I found the options, debug options, enable replication manager for RAM device...didn't see that before, lol This is for debug purposes only. For exam...

The update procedure is in Release Notes (Information) section of StarWind installer.

Also, can an upgrade be done without downtime (i.e. one node at a time) and without a full resync of the cluster?

yes!

From both sides of the mirror?

What do you mean?

In case of 2-Node clustered device you should disconnect 2 iSCSI targets on the client side and remove 2 iSCSI targets (1 on each storage node).

Disconnect the targets in iSCSI initiator, revome the targets in StarWind Management console.