HA storage with L2 cache and Invalid partner info error

epalombizio · Tue Nov 18, 2014 2:29 pm

Correct, using 7354. This was a fresh installation on a fresh installation of Windows 2012 R2.

Elvis

epalombizio · Tue Nov 18, 2014 3:20 pm

Tried all the quirky workarounds listed in the post. FWIW, I'm not attempting to use an L2 cache. Just a simple HA setup is failing for me. I forwarded this to premiumsupport for help since I paid for support, hopefully will have some answers soon!

Thanks

thefinkster · Tue Nov 18, 2014 3:57 pm

Hey.

Remove the servers from your console and re-add them and try this again.

I think this is a bug in 7354.

epalombizio · Tue Nov 18, 2014 6:59 pm

Removing and reading worked.. Also, it stated that both units were part of a cluster, so I removed their membership in the cluster as well.
Looks like I'm fine now.

thefinkster · Tue Nov 18, 2014 7:13 pm

Yea. Clustering is not something that I'd recommend at this time, since all it does is assist in the manual process of establishing HA partners. On top of not allowing us to select all the individual locations for the images/SWDSKs/etc, it's just not ready for prime time.

epalombizio · Tue Nov 18, 2014 7:15 pm

Thanks for your help finkster!.. In another post, I asked that Starwind consider a sticky post, or other centralized area to aggregate features that are production ready, beta, and experimental.. It'd really help everyone in the forums stay informed!!

thefinkster · Tue Nov 18, 2014 7:43 pm

Yea.

This is definitely a product where you have to :
1) read all the whitepapers (from oldest to newest).
2) read all forum posts; including older ones
3) communicate with support@starwindsoftware.com to verify everything that might still be questionable in your own mind.

They do sticky some stuff (IP settings, etc); but nothing of any new forum revelations discovered by our testing. More testers (who actually have dedicated time to test) of all the various scenarios is something I think is missing; or the HA creation bug (re-add the servers) wouldn't have made it through QA.

Fri Nov 21, 2014 4:18 pm

Thanks you for sharing your feedback with us - we really appreciate it.
We are usually not considering recreating of the device as the #1 troubleshooting step since it is something like "in any weird situation reinstal Windows", which we don`t really like to do.

Also, if you have some ideas or feature request - fell free to drop me a quick email (av@starwind.com).

usovvova1 · Sat Mar 25, 2017 2:54 pm

solution for those who faced this issue: you just need to name your image files on two nodes DIFFERENTLY!

[ ... ]

Sat Mar 25, 2017 7:05 pm

Duly noted! I'll file a bug. Thank you!

usovvova1 wrote:solution for those who faced this issue: you just need to name your image files on two nodes DIFFERENTLY!

[ ... ]

Thu Mar 30, 2017 7:15 pm

Hello usovvova1,
I have checked if the issue can be reproduced in the latest build and was not able to reproduce it.
I believe the issue was resolved more than one year ago - in the build 8730.
Please, let us know if the issue will still persist in the latest build.