Upgrading to PowerVC for Private Cloud 2.2.0

Before you begin

PowerVC 2.2.0 version supports the Private Cloud Edition only. You can now directly upgrade to PowerVC for Private Cloud 2.2.0 by using any of these options.
  • If you have a previous version of PowerVC 2.1.0 or later, take a backup and restore the backup on a different system that has PowerVC for Private Cloud 2.2.0 installed.
  • If you have a previous version of PowerVC 2.1.0 or later installed and want to upgrade to PowerVC for Private Cloud 2.2.0 by using the rolling upgrade or offline upgrade process, first run the powervc-opsmgr private_cloud --enable OpsMgr command to move to PowerVC for Private Cloud 2.1.0 or later. Then, upgrade to PowerVC for Private Cloud 2.2.0.
  • If you want to move to SLES 15 SP3 SAP Edition in PowerVC for Private Cloud 2.2.0, take a backup from PowerVC 2.1.0 SLES 15 SP3 or later and restore to PowerVC for Private Cloud 2.2.0 SLES 15 SP3 SAP Edition.
Note: If you have a previous version of PowerVC 2.1.0 or later installed with PowerVC or PowerVC for Private Cloud offering, you can take a backup and restore on PowerVC for Private Cloud 2.2.0.

PowerVC 2.2.0 supports NovaLink 2.2.0 only. Before upgrading to PowerVC 2.2.0, we recommend you upgrade to the latest NovaLink version.

PowerVC provides you three methods of upgrading, through backup and restore, offline upgrade, and rolling upgrade.

  • Backup and restore - In backup and restore method, you can choose to upgrade PowerVC on the same system where you have earlier version installed or on a different system. This topic details the procedure for backup and restore method.
  • Offline upgrade - For offline upgrade, you can upgrade all nodes simultaneously in a multinode environment even when services are offline. This method is only supported when you upgrade from PowerVC versions 2.1.0 or later to 2.2.0. For details, see PowerVC offline upgrade.
  • Rolling upgrade - If you are upgrading through rolling upgrade method, you can upgrade PowerVC only on the same system. This method is only supported when you upgrade from PowerVC versions 2.1.0 or later to 2.2.0.
  • After upgrading to PowerVC 2.2.0, it is recommended that you visit Fix Central to download and install any fix packs that are available. For more information, see the Getting fixes from Fix Central topic.
  • To maintain PowerVC cluster consistency, restart controller node one at a time. Make sure that you allow 30 minutes before you restart the next node.
Upgrade considerations
Consider the following before you start with install or upgrade procedure.
  • Make sure that the managed hosts are on IBM POWER8® or later.
  • Review the hardware and software requirements.
  • For RHEL and SLES, PowerVC 2.2.0 installation is supported on both single node and multinode environments.
  • Before performing any operation, make sure that the VM hostname is same as the hostname that you used to create the inventory.
  • Before upgrading to PowerVC version 2.2.0, migrate any hosts running on Compute plane node to PowerVC controller by using /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST>. After upgrade process is completed, you can migrate the hosts back to Compute plane node by using /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST>.
  • Support for IBM XIV® Storage System and EMC VNX has been withdrawn.
  • If backup cluster has root user credentials and restore cluster has sudo user credentials then the restore cluster will have login enabled for both root and sudo users after restore operation is completed.
  • Compute plane node must be removed and added later in a scenario where backup is being taken using root user credentials and restore is performed by using sudo credentials.

Upgrade options for PowerVC legacy versions

About this task

If you have any previous legacy version of PowerVC 2.1.0 or later, you can upgrade by using any of these options.
  • Upgrade to 2.2.0 legacy using the backup and restore procedure.
  • Take a backup of PowerVC 2.1.0 legacy or later and restore to PowerVC 2.2.0 in a single or multinode environment.

Legacy install of PowerVC is not supported for add node, replace node, resync node, backup node, and compute plane node registration.

Taking backup of PowerVC

About this task

For PowerVC 2.1.0 or later versions, complete these steps. This procedure is supported only for HA or clustered environment.
  1. Ensure that the user has sufficient sudo privileges configured to perform execution of this command and read access to the files.
  2. Run the powervc-opsmgr backup command with any needed options. Perform Novalink upgrade to the latest version.
    Listed here is the upgrade combination.
    Backup of PowerVC 2.1.x can be restored on PowerVC version 2.2.0 running on RHEL or SLES OS.
When the backup operation completes, a new file powervc_backup.tar.gz is placed in a new time stamp subdirectory of the target directory. For example, a potential file path is /var/opt/ibm/powervc/backups/<timestamp>/powervc_backup.tar.gz. You can then leave the archive there or move or copy it to another directory as needed.
Note: If an error occurs while running powervc-opsmgr backup, check for errors in the powervc-opsmgr backup logs in /opt/ibm/powervc/log.

You can also refer to Backing up for more information on backup procedure.

Restoring to PowerVC version 2.2.0

About this task

Review operating system requirements at hardware and software requirements. If restore fails due to network disconnection or any other reason, you can re-run powervc-opsmgr restore -c <CLUSTER_NAME> to resume the restore operation.

If PowerVC version 2.2.0 is using the local OS registry (and not the LDAP server) as the backend for authentication, then ensure all local OS users existing (for authentication) on the PowerVC version 2.1.0 or later system are also created on the PowerVC version 2.2.0 system before restore is performed. This prevents any user login issues after restore.

In PowerVC, there are two options available for upgrade in a clustered or HA environment.
  • PowerVC restore on single node. You can move to three node cluster using powervc-opsmgr addnodes command.
  • PowerVC restore on single node and multinode (three nodes). To restore on single node or multinode, run powervc-opsmgr restore command. Later, you can add two more nodes making it a five node cluster by running the powervc-opsmgr addnodes command.
    Note: When restoring in a multinode environment, make sure you perform restore on the primary node.

Perform these steps to restore the backup from PowerVC version 2.1.0 or later (for HA environment or legacy install of PowerVC) to 2.2.0. Before starting with the restore steps, ensure that the target system is properly prepared and all services of PowerVC are in running state.


  1. Copy the backup file to the system where PowerVC version 2.2.0 is installed. Perform this step if you are upgrading PowerVC on a different system.
  2. Run # powervc-opsmgr restore to restore PowerVC from backup. This restore command looks for backup archive at /var/opt/powervc/backups directory by default.
    # powervc-opsmgr restore -c <clustername> -b <backup archive file path>

    Additional PowerVC nodes can be added to the cluster to make it multinode environment. For details, see PowerVC Operations Manager.

    • After a successful restore, if another restore is triggered on the same system make sure /var/opt/ibm/powervc/backups/<powervc_release>/ is removed or moved to a different location to avoid conflicts.
    • When restore operation is performed on a fresh system, the PowerVC services running on NovaLink host are upgraded to the latest version.

Update PowerVC on the NovaLink host

About this task

As part of PowerVC upgrade, the PowerVC components running on NovaLink are automatically updated.

If the NovaLink host is down during upgrade or restore procedure, the admin user can log in to the PowerVC UI and click Finish Update NovaLink after the host is up and running. This action updates only the PowerVC components running on NovaLink and does not update NovaLink version.

  • If you are planning to re-install OS on NovaLink, it should be done prior to PowerVC upgrade. After successful upgrade and restore if the NovaLink is brought down to re-install the OS, PowerVC cannot connect back automatically. In such a case, please contact support team.
  • For RHEL 9.x, make sure that the CRB repo is enabled.

NovaLink update procedure

Note: Consider the update procedure only if you are upgrading OS on NovaLink host to RHEL 9.x.
Once PowerVC restore or upgrade is completed on version 2.2.0, perform the following steps.
  • Move hosts into maintenance mode in PowerVC 2.2.0.
  • On the NovaLink host, re-install operating system to RHEL 9.x.

    If you have changed the NovaLink credentials during OS re-installation process, or if the host is registered to PowerVC via ssh key based authentication prior to re-installation, then you must update username and password in Edit Host Connection section of the Host details page.

  • Make sure NovaLink 2.2.0 is properly installed.
  • Exit hosts from the maintenance mode.
  • From primary or bootstrap node, add backup file permission by running chmod 644 /var/opt/ibm/powervc/backups/powervc_backup.tar.gz.
  • Login to PowerVC 2.2.0 GUI, update NovaLink and wait until upgrade completes. You can choose one of the following methods to update NovaLink.
    • On the Overview page, click Update NovaLink in the notification to finish updating NovaLink.
    • Navigate to the Hosts page and click Finish Update NovaLink.