One of my readers asked me if I could write down the steps required to upgrade an HP StoreVirtual (P4500) SAN environment (Thanks Hal!). Instead of updating the original post, I am publishing this post to make it easier to find for other people. This is a general instruction for version 9.5 and higher.
- Download all upgrade files. Open the Centralized Management Console (CMC) on your management server and go to “Configuration Summary”. This action will take some time as it will download all files needed for the upgrade (in my case about 4GB and took some hours).
- Upgrade CMC. Go to the Configuration Summary page and click the Continue button right next to the CMC part. This upgrade can happen way before the actual upgrade of your storage nodes.
- Upgrade the HP CLI, HP Application Aware Snapshot Manager and HP DSM for MPIO software on machines that are using them. The binaries can be found in the download directory of CMC (Go to Help, Preferences and click Upgrades. The Download Directory is shown there). During the upgrade wizard during step 6 it will actually ask you if you are using any of these products and that you have to upgrade them prior to upgrading the storage nodes and Failover Manager.
- Make sure all of your volumes are protected with Network RAID-10 to prevent downtime of these volumes when upgrading the storage nodes.
- Increase the Bandwidth Slider thru CMC by editing the Management Group your are upgrading. This will speed up the actual restripe done after each node upgrade and will decrease the total time you need to upgrade the storage nodes. Note: Only increase the bandwidth slider if your SAN is running a low load. If you don’t know if this is the case, leave it set to default or your own custom value.
- Upgrade your Management Group(s). Use the Configuration Summary page for this again and click Continue next to the name of your Management Group. You can select specific patches or versions here for your storage nodes and for your deployed Failover Manager if you have any. After clicking Continue the upgrade process will take off and the rest of the process is fully automated. CMC will make sure that redundancy is maintained by upgrading nodes not dependent of each other. Note: If you are using SmartClone volumes (Remote snapshots) the associated schedules will be put on pause during the upgrade.
- Wait :-). The Failover Manager is upgraded first, next are the storage nodes. Each node will need about 30 minutes to be upgraded. Starting with LeftHand OS 10.0 upgrades will no longer require a reboot of the node but instead will perform a restart of the storage services as far as I know, which will decrease the time to upgrade drastically. Next month I will probably upgrade our nodes to LeftHand OS 11.0 when it’s released and will write a post about it.
- Celebrate! You’re done =) Don’t forget to restore the bandwidth slider if you changed it during step 5.
Thanks for reading, feedback is always welcome!
- Upgrading to LeftHand OS 10.5 (snowvm.wordpress.com)