6. Automatic check and promotion in case all nodes were restarted; 12. HOT option to enable/disable L1 or/and L2 cache; 13. HOT option to change WT<=>WB L2 cache mode; +1 These are must have for high-grade production! * Automatic poweron in case of failure of all nodes is a request done for years! ...

Hi Anton et al, I have sent several times an e-mail to license@starwind.com asking for a 2-node free license. But nobody answered. Please, is limited in some sense this free license? What is needed to be qualified for it? It would seem logical that at least messages be answered. Do you have any tech...

Anatoly (staff) wrote:I`m glad that we are on the same page now.

Well, lets wait for the good news:)

Great! Please, send me info when a beta is available for testing.

Regards!

Hi Anton,

Thank you for, at least, checking the current behaviour and for think to incorporate a simple solution in the future.

I hope to receive good news in the next (or following) version.

Regards!

Instead of looking @ other software you need to re-think what you're doing. If you're putting up all nodes being down there's no way to know whose data is the mos recent one. You cannot trust to time recorded in log as if cluster went down - time may go out of sync as well. You need to power up the...

danisoto: If you shut down node A and run on node B for a few minutes.. then you shut down node B also. Scenario 3: Both nodes start, and when they can exchange "info" the sync process from the correct partner starts. Hi Lohelle, Our concern is about both nodes running AND both marked as ...

danisoto: If you shut down node A and run on node B for a few minutes.. then you shut down node B also. Scenario 1: You turn on only node A. You really do not want node A to start serving clients automaticly, as this is not the most recent data. Scenario 2: You turn on only node B. This "shoul...

Hi Anatoly, I like to clarify: Our tests with the last version don't work as you described in some (critical) cases. Test environment: * Windows 2012 * StarWind iSCSI SAN v6.0.0 (Build 20121115, [SwSAN], Win64) Free license * Device1: IBV1 40GB on node A (name: "40gb-primary") * Device2: I...

Hi Anton,

Shocking news for us! In this case we need to search for another software.
Why not put this functions as optional?

Regards!

Hi, After testing the last release of iSCSI target with HA support (great! 128GB for free is good for our tests), I found that the current implementation it is not enough for Fault Tolerant services . We do several tests, but this one is very descriptive (Build 20121115): * Two nodes (A and B) with ...

hmm i had a similar occurance to this occur the other week. what happens then when you have HA running both have a hard crash, but because you run multipath and some servers are using the alt. path when you force bring up one node it causes massive issues because its not the most recent data for th...

Max (staff) wrote:Let's say that it will be one of the new features included.

I feel that the next version v6 will be a huge improvement in the HA scenario!

I'll be waiting impatiently to test it.

Do yo have any idea I could find a requirements for what should be done @ target side to support such a scenario? From what I've seen there were either configuration manuals how to enable ALUA on some array or papers describing why other array cannot work in AULA (b/c of deadlocks). So your feedbac...

@ziz (staff) wrote:Sorry, we do not publish such information (planed functionalities) in the forum.

Ok, but we can assume that the next version 6 will include it?

anton (staff) wrote:Stay tuned. Hope to have this one on V6 schedule

So, please, consider the two timeouts: the first is when both nodes are up, the second when only one is up and the other is down (or you fell that is down!).