I've observed something similar in the lab. I just put it down to me messing around a lot but maybe not.

Cheers, Rob.

PS. Which version BTW?

Ahh right so it's a data migration and not an in-place upgrade? So you therefore can't upgrade v6 to v8 on the same server?

Cheers, Rob.

BTW, have you singed in to our Beta-testing program?

Well you sent me the t-shirt so I assume so?? But I haven't personally signed up for anything.

Cheers, Rob.

BTW - whatever the current system does, it's confusing as it's separated the setting from the comment: <!-- Allow listing of interfaces in response to SendTargets=All --> HERE IS THE COMMENT <!-- <iScsiDiscoveryListInterfaces value="1"/> --> THIS DOES NOTHING <!--Force set of default param...

Hi Bodan, You are indeed correct. It's not at the end though - the uncommented line is at line 92 but there are TWO uncommented lines at line 105 & 106: <LocalizationDir value="Localizations"/> <iScsiDiscoveryListInterfaces value="1"/> <iScsiDiscoveryListInterfaces value=&quo...

Is this an instant process or does it have to go through some kind of conversion?

Cheers, Rob.

PS. Apologies for teaching granny to suck eggs but I just want this to work Also, appreciate split-brain is a risk but I think the above circumvents this.

I've discussed the situation with developers and it looks like there's a major confusion as my information was a bit outdated: I'd like to propose my idea, just my 2 cents, on how to manage this kind of situation. You wrote that each node sharing the storage is able to log the time of the last upda...

I believe that v8 doesn't support the IBV (thin provisioned) format with the only thin-provisioned format being the LSFS based one.

So what happens to your IBV storage when you upgrade to v8?

Cheers, Rob.

PS. I may have asked this before but can't recall the answer!

BTW - this video was recorded using Microsoft's ScreenRecorder which doesn't generate key frames very often (to keep the file size small) so fast forwarding through the video isn't that easy.

Cheers, Rob.

I've produced a video to demonstrate this issue as I'm not sure you believe me! :D https://dl.dropboxusercontent.com/u/36684956/StarWind01.wmv Timeline: 00:00 Two node StarWind cluster already exists with no storage 00:04 Create Storage1 as 5GB of thick HA storage on both nodes 00:36 Wait for 2nd no...

PS. I typed that entire last post whilst waiting for "fast" synchronisation to complete. It's only got to 13% after 15+ minutes. Something is definitely amiss here - all caches will have been flushed and replication was in sync. On restarting the service, zero bytes should of been out of s...

More information on unusual activity on automatic synchronisation. I was watching the Resource Monitor carefully as the "Creating" state went through all of the SPSPX files and re-read them. After it had done this, it's gone into "fast synchronisation" and has been for about the ...

Allied with all the tests about automatic resync after node down time, I've stopped and re-started the StarWind service on one node. Automatic resync has indeed kicked in but it was taking a lot longer than last time I tried this. However, this time, my LSFS storage is much bigger (275GB): sshot-60....

OK, so this is how it works now. After all cluster nodes were down and now are up StarWind is ... Hmm sort of but the devil is in the detail here. Depends what you mean by all cluster nodes were down? I'm not talking here about stopping & starting StarWindService alone here. I talking about tak...