Got that update already, we have multiple systems running here,
but they were all updated some time before to up80,
before we went to up90.
I'll give it a try.
Looking to our systems already running on up90,
the failover on I/O errors is already enabled by default
so we don't have to configure this.
Good idea, because we could not configure this anyway,
since for configuration changes we would have to stop failover...
The update from build up55.5087 to up90.5845 should be done with no issues.
Just in case if you face any issue with updateing old system to a newer one, you may ask for a small update ( upd_0756 ) from the support team.
What raid controller are you using and what firmware version is it at?
I've had lots of issues with previous firmware versions (3.66 and 2.00) for HP Smart Array P410 when using SATA disks.
I'm in the same boat and currently running 5087 and want to get to the latest. When I went thru the update check it only found 5626 instead of 5845 as I was expecting. Is there a reason the Update Check isn't going to 5845?
Also will any of these updates affect failover (virtual IP). I notice it said something in the change notes for 5626 that now all IP would have the auxillary connection set for each of you nics, didn't know if that would affect anything.
Andy,
The auto-updater gets the next build in line.
In your case, just download the latest ISO in your user portal, and upload it manually to the webGUI.
The aux requirement is not in the latest build, so you are ok to move to the latest build.
We've tested these feature and removed (e.g) disk for disk in a raid5 system.
"Degraded" mode (removing one disk) doesn't trigger the failover. Only a failed/broken raid volume leads to it.
This was our experience in our testing environment.
Senior Member
Posting Permissions
Reply With Quote