When I try to connect to my starwind server through the console I get starwind service not found on host XXX.
I did find an article on this and one option was to restart the starwind service on the server. That's great but what happens if I restart that service when I have multiple critical servers hanging off the LUN's. Another fix was simply reinstall the product. All of this sounds scary when you have production servers still working on this. I simply can manage it through the console. Is there a sensible fix detailing what the risks are if I do x y z. I guess this is where you get what you pay for. Ive worked with many SAN systems but never have I seen such scenarios where I loose complete control of a SAN with such drastic measures to fix them. PS I also have a DR Starwind SAN and I have similar, the console connects and then it goes none responsive. So I have 2 starwind SAN's on the same customer site that I can no longer manage. Does anyone have any ideas how to fix these issues.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software