You may have seen my Fusion upgrade article and now this one is about upgrading NexentaStor to the current GA (5.1.2). Regardless of the version this article will be updated so you know it works.
I can confirm it is OK to upgrade Fusion first, and NexentaStor second, and I think that is the right way to do it.
I also recommend you follow the exact steps of my upgrade as in the past they worked and slightly different steps did not.
There is no other prep work other than having a backup of what you are running on your Nexenta. Which I do but as I am not in an HA cluster I will be rebooting the array so I need to have the VMs on it powered off. If I was in a cluster there would be no outage.
- Log in on the console via SSH.
- Execute software version to see what your current version is.
- We can see that 5.1.1 is my current.
- Now use the software upgrade -n to see what is available.
- We can see there is outstanding updates.
- So we now use software upgrade to do the upgrade.
- The download finishes soon.
- We see the upgrade start. In 184.108.40.206 it was 258.2 MB and it took longer than 220.127.116.11. For 5.1.1 it did not take as long to reboot stage. In 5.1.2 it was 135.4 MB. In 5.2.0-FP1 it was 175.6 MB.
- Before you know it (with 5.1 there was likely 25 minutes wait, but 5.1.1 was maybe 5 minutes, and 5.1.2 was maybe 20 minutes) you have a prompt to restart.
- And we do.
- When it restarts and we can see the console looks healthy we use Fusion to see if things worked. With the 5.0.3 to 5.1 upgrade it took perhaps 25 minutes after saying Y to reboot before it actually did. For 5.5.1 it took only maybe 10 minutes. I was not able after that to SSH to the array so I checked the console. It appeared to be hung (on the SUNOS Release 5.11), so I powered off and powered on. It seemed to hang again and it took quite some time but it eventually booted and all was good. So instead of the 25 minutes previously I would say 60 – 90 minutes.
When we log in to Fusion, we can see on the Administration page of the appliance that it is using 5.1.2 (or whatever is latest) now.
Or, if we look on the console after we have logged in, we can also see the version.
So I start my VMs and all is good.
- 2/2/19 – from 5.1.2 to 5.2.0-FP1.
- 7/22/18 – from 5.1.1 to 5.1.2.
- 3/4/18 – from 5.1.0 to 5.1.1 FP1.
- 11/5/17 – this was used to upgrade from 5.0.6 to 18.104.22.168.
- 4/16/17 – release. This was the 5.0.2 to 22.214.171.124 upgrade
=== END ===