StarWind Software

Hi Everybody,
about three weeks ago, I updated the classic iSCSI-HA from v5.8 to the latest v6.0. Followed the guides, check sync, update one node, reboot, wait for sync, updated the partner, restart and sync again.
Everything worked fine, the two 2008R2 failover nodes did not loose any data nor even recognized a missing resouce. Between the two client-nodes are 2 x 2 mpio paths to the two StarwindSoftware servers.
Thanks to a real smooth update scenario.

BUT.... last week I made Windows updates (on one of the StarwindSoftware servers) and the 2008r2 cluster / nodes lost the cluster shared volumes .
Even without win updates, just a shutdown of the iSCSI service leads to loosing the csv's (mostly, sometimes one csv from four is still there).

Any ideas?

Thx
Raymond

Nice... Any chance to see a StarWind log matching broken cluster?

Hi Anton,
I could send you a zip file with the log.... How?

Additional information, could the strange behavior depend on a trial version of the hyper-v backup plugin?

THX
Raymond

Hi!
You can send the logs to support@starwindsoftware.com (please put the link to this disscussion in the email), We require StarWind logs and WinSys and App logs (last two in *.csv format) from all issued SAN boxes.

In my opinion there is something with the networking (that is just a guess).

As about the backup plug-in - it shouldn`t affect CSV, afaik.

It can be a Windows problem.

I think Starwind should define a policy like Ne tapp for example.

They require the following Windows Hotfixes for 2008 R2 as a startup point.

Hotfix When required Filename
2528357 Always Storport.sys
2754704 Always Mpio.sys
2684681 Always Iscsilog.dll

It can be a Windows problem.

Totally agree.

I think Starwind should define a policy

Would you please clarify that?

Thanks

The policy, is about the requirements of the installation to receive support.

For example Netaapp, requires the above hotfix list to be installed (the hotfixes are not available trough windows update, they need to be manually installed). Those hotfixes fix ISCSI and Cluster problems.

Usually they post the hotfixes that contain the latest versions of the most significant files (Storport.sys, Mpio.sys ,Iscsilog.dll).

If you check the version of Mpio.sys (for example) of a Windows 2008 R2 SP1 updated through Windows Update, you can see that the version is very old.

Microsoft recommendations:

http://social.technet.microsoft.com/wik ... 1-sp1.aspx

Alexpt,
Thank's for the idea!
I'll ask our team to modify the system requirements and add this to our best practices document.