StarWind Software

Hi,

I’ve noticed that whenever I refresh the targets while it is doing synchronization, Starwind application would crash.

I am running 5.6 with windows 2008 r2 sp1.

Is that a known bug, I am able to duplicated the issue with two of my server.


Problem signature:
Problem Event Name: BEX
Application Name: StarWindManagementConsole.exe
Application Version: 5.6.0.1659
Application Timestamp: 4d53ea6c
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 4c244c8b
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.400.8
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Not a known issue. Could you please catch the situation and send us zipped .dmp and .log files to support@starwindsoftware.com for our R&D assistance. Thank you for cooperation!

I had that issue too.

You aren't running the latest version. 1667 is the latest. They updated from 1659 sometime a week or two after posting 5.6 was available. Seems to have taken care/helped the issue, so just redownload and you should have the newer version.

Wow! Thank you for taking care of this one

kmax wrote:I had that issue too.

You aren't running the latest version. 1667 is the latest. They updated from 1659 sometime a week or two after posting 5.6 was available. Seems to have taken care/helped the issue, so just redownload and you should have the newer version.

anton (staff) wrote:Wow! Thank you for taking care of this one

kmax wrote:I had that issue too.

You aren't running the latest version. 1667 is the latest. They updated from 1659 sometime a week or two after posting 5.6 was available. Seems to have taken care/helped the issue, so just redownload and you should have the newer version.

Not a problem, I was going to mention that a while back but forgot, since the latest version thread didn't mention anything. Version 5.6 was announced on 2/14 which at the time was version 1659 and only by downloading it again I noticed the revision level increased. So I guess in the latest version thread posting revision level would be helpful.

We'll do it! Just trying to keep version updates not very frequent not to scare the customers

kmax wrote:

anton (staff) wrote:Wow! Thank you for taking care of this one

kmax wrote:I had that issue too.

You aren't running the latest version. 1667 is the latest. They updated from 1659 sometime a week or two after posting 5.6 was available. Seems to have taken care/helped the issue, so just redownload and you should have the newer version.

Not a problem, I was going to mention that a while back but forgot, since the latest version thread didn't mention anything. Version 5.6 was announced on 2/14 which at the time was version 1659 and only by downloading it again I noticed the revision level increased. So I guess in the latest version thread posting revision level would be helpful.

great, good to know, let me download it again and try it.
I will report back.

ETA on 5.7 ?

Great, I can report back that the crashing issue is resolved with upgrading to 1667. Thanks !

Would be very much appreciated! Thank you!

oxyi wrote:Great, I can report back that the crashing issue is resolved with upgrading to 1667. Thanks !

V5.7 should be published gold in 2-3 weeks from now. We're stalled a little bit with ESX certification.

oxyi wrote:great, good to know, let me download it again and try it.
I will report back.

ETA on 5.7 ?

anton (staff) wrote:V5.7 should be published gold in 2-3 weeks from now. We're stalled a little bit with ESX certification.

oxyi wrote:great, good to know, let me download it again and try it.
I will report back.

ETA on 5.7 ?

Can you throw us a bone and tell us exactly what 5.7 has?

Here are some of the improvements:
Multiple routes for HA nodes cross-link. Better HA performance and more redundancy. No NIC teaming any more. We'll combine and multiplex every possible data route between nodes.

10 GbE and 40 GbE related peformance optimizations. For both HA and non-HA versions.

Bandwidth throttling for synchronization. No more rejected incoming connections for shared data storage while doing HA sync. Both automatic and manual control mode.

De-duplication with 4KB and 8KB block sizes. MUCH faster (2x-3x times compared to 512 byte block) and up to 10x times less memory footprint. With 10-15% space lost compared to 512 byte de-duplication block.

Stay tuned!

Max (staff) wrote:Here are some of the improvements:
Multiple routes for HA nodes cross-link. Better HA performance and more redundancy. No NIC teaming any more. We'll combine and multiplex every possible data route between nodes.

10 GbE and 40 GbE related peformance optimizations. For both HA and non-HA versions.

Bandwidth throttling for synchronization. No more rejected incoming connections for shared data storage while doing HA sync. Both automatic and manual control mode.

De-duplication with 4KB and 8KB block sizes. MUCH faster (2x-3x times compared to 512 byte block) and up to 10x times less memory footprint. With 10-15% space lost compared to 512 byte de-duplication block.

Stay tuned!

Any ETA on this yet? I could really stand to have much faster sync. My slowest RAID's in the StarWind boxes write about 10X as fast as the sync over 10GbE right now.

Mid-summer I guess.

As we're far away from original question set I'm closing this thread as answered.

== thread closed ==