Upgrading to PowerVC for Private Cloud 2.3.0
Before you begin
PowerVC 2.3.0 supports the Private Cloud Edition only. PowerVC 2.3.0 supports NovaLink 2.3.0 only. Before you upgrade to PowerVC 2.30, it is recommended to upgrade to the latest NovaLink version.
For more information about upgrading PowerVM® NovaLink on an RHEL 8.x partition, see Upgrading PowerVM NovaLink 2.1.1, or later to 2.3.0 on an RHEL 8.10 partition.
For more information about upgrading PowerVM NovaLink on an RHEL 9.x partition, see Upgrading PowerVM NovaLink 2.1.1, or later to 2.3.0 on an RHEL 9.2 partition.
PowerVC provides you three methods of
upgrading, through backup and restore
, offline upgrade
, and rolling
upgrade
.
- Backup and restore
- In the
backup and restore
method, you can choose to upgrade PowerVC on the same system where you have an earlier version that is installed or on a different system. For details, see Backing up. - Offline upgrade
- For "offline upgrade", you can upgrade all nodes simultaneously in a multinode environment even when services are offline. For details, see PowerVC offline upgrade.
- Rolling upgrade
- If you are upgrading through the "rolling method", you can upgrade PowerVC only on the same system. For details, see PowerVC rolling upgrade.
You can directly upgrade to PowerVC for Private Cloud 2.3.0 by using any of the following options:
| Operating system (OS) | Previous OS versions | Previous PowerVC versions | Upgrade OS versions | PowerVC upgrade options |
|---|---|---|---|---|
| RHEL | 8.x and 9.x | PowerVC 2.2.0 | 8.x and 9.x |
|
| RHEL | 8.x and 9.x | PowerVC 2.2.1 or 2.2.1.1 | 8.x and 9.x |
|
| SLES | SLES 15 SP3 SAP Edition | PowerVC for Private Cloud 2.2.0 and 2.2.1 | SLES 15 SP5 SAP Edition |
|
| SLES | SLES 15 SP5 or SLES 15 SP5 SAP Edition | PowerVC 2.2.1 or 2.2.1.1 | SLES 15 SP5 or SLES 15 SP5 SAP Edition | Backup and restore. See Backing up. |
Notes:
- Before you install or upgrade, make sure that the priority number of the PowerVC repository is higher than the RHEL or SUSE Linux® Enterprise (SLES) system OS repository. The repositories that PowerVC creates have 90 as the priority in which 1 is the highest and 99 is the lowest.
- After you upgrade to PowerVC 2.3.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.
- If you have a previous version of PowerVC 2.2.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.3.0.
- If you want to move to the latest supported RHEL version, make sure to successfully upgrade to PowerVC for Private Cloud 2.3.0 first.
- 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.3.0 installation is supported on both single node and multinode environments.
- Before you perform any operation, make sure that the VM hostname is the same as the hostname that you used to create the inventory.
- Before you upgrade to PowerVC version 2.3.0, migrate any hosts that runs on Compute plane node to PowerVC controller by using the /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST> command. After upgrade process is complete, you can migrate the hosts back to Compute plane node by using the /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST> command.
- Support for IBM XIV® Storage System and EMC VNX is withdrawn.
- It is recommended to update the operating system distribution before you
upgrade to PowerVC 2.3.0, or later
versions. If the operating system distribution is not updated before the update process, then it is
mandatory to update the OpenSSH server to the latest version. Note: If the OpenSSH server is not updated to the latest version, it might lead to issues during the upgrade process.Before you proceed with PowerVC upgrade, perform the following steps to update the OpenSSH server to the latest version:
- Run the following command:
yum update openssh-server - Restart the SSHD service.
- Run the following command:
Notes:
- If backup cluster has root user credentials and the restore cluster has sudo user credentials then the restore cluster has login enabled for both root and sudo users after the restore operation is complete.
- Compute plane node must be removed and added later in a scenario where backup is taken by 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.2.0 or 2.2.1, you can upgrade by
using any of these options.
- Take a backup of PowerVC 2.2.0 or 2.2.1 legacy and restore to PowerVC 2.3.0 in a single or multinode environment.
Taking backup of PowerVC
About this task
For PowerVC 2.3.0 or later versions,
complete these steps. This procedure is supported only for HA or clustered environment.
- Ensure that the user has sufficient sudo privileges that are configured to perform execution of this command and read access to the files.
- Run the powervc-opsmgr backup command with any needed options. Perform
Novalink upgrade to the latest version.Note: Backup of PowerVC 2.2.x can be restored on PowerVC version 2.3.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 the powervc-opsmgr backup command is running, 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.3.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.3.0 is using the local OS registry (and not the LDAP server) as the backend for authentication, then ensure all local OS users that exists (for authentication) on the PowerVC version 2.2.0, 2.2.1, or 2.2.1.1 system are also created on the PowerVC version 2.3.0 system before restore is performed. This action prevents any user login issues after restore.
In PowerVC, two
options are available to upgrade in a clustered or HA environment.
- PowerVC restore on a single node. You can move to three node cluster by 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 that makes it a five node cluster by
running the powervc-opsmgr addnodes command.Note: When you restore in a multinode environment, make sure that you perform restore on the primary node.
To restore the backup from PowerVC version
2.2.0, 2.2.1, or 2.2.1.1 or later (for HA environment or legacy installation of PowerVC) to PowerVC 2.3.0 perform the following steps:
Note: Before you start with the restore steps, ensure that the target system is properly prepared
and all services of PowerVC are in running
state.