Upgrading the Virtual I/O Server - non-SSP cluster

Learn about the process of upgrading or migrating the Virtual I/O Server (VIOS), when the VIOS does not belong to a Shared Storage Pool (SSP) cluster.

You can directly migrate the VIOS from VIOS version 2.2.x.x to VIOS version 3.1, if VIOS does not belong to a Shared Storage Pool (SSP) cluster. The different upgrade processes are explained in the following sections.

Using the viosupgrade command with the bosinst option from NIM Master

Virtual I/O Servers from VIOS version 2.2.x.x to VIOS version 3.1 can be upgraded by using the viosupgrade command from the NIM bosinst method.

For a VIOS node that is at version 2.2.4.x or 2.2.5.x and that must be upgraded to version 3.1.0.00, the VIOS node can be directly upgraded to version 3.1.0.00, by using the following command:

viosupgrade -t bosinst -n <hostname> -m <mksysb_image> -p <spot_name> -a <hdisk>

For example: viosupgrade -t bosinst -n vios1 -m vios_3.1.0.0 -p vios_3.1.0.0_spot -a hdisk1

You can check the status of the VIOS installation by using the viosupgrade -q vios1 command.

Using the viosupgrade command with the altdisk option from NIM Master

Virtual I/O Servers from VIOS version 2.2.6.30 to VIOS version 3.1 can be upgraded by using the viosupgrade command from the NIM altdisk method.

The VIOS can be upgraded to version 3.1.0.00, by using the following command:

viosupgrade -t altdisk -n <hostname> -m mksysb_image> -p <spot_name> -a <hdisk>

For example: viosupgrade -t altdisk -n vios1 -m vios_3.1.0.0 -p vios_3.1.0.0_spot -a hdisk1

You can check the status of the VIOS installation by using the viosupgrade -q vios1 command.

Note: The viosupgrade -t altdisk command is supported in VIOS version 2.2.6.30, or later. Hence, this option is not applicable for upgrades where the VIOS is at versions earlier than 2.2.6.30.

Using the viosupgrade command from VIOS - Non-NIM environment

Virtual I/O Servers from VIOS version 2.2.6.30 to VIOS version 3.1.0.00, or later, can be upgraded by using the viosupgrade command. In this way, you can upgrade a VIOS in a non-NIM environment, where it uses the alt_disk_mksysb command to install VIOS version 3.1.0.00 on the provided disk.

You can upgrade the VIOS, by using the following command:

viosupgrade -l -i <mksysb image> -a <hdisk>

For example: viosupgrade -l -i vios3.1_mksysb -a hdisk1

You can check the status of the VIOS installation by using the viosupgrade -l -q command.

Traditional method - manual

In the traditional method, you must back up the VIOS metadata by using the viosbr -backup command, save the backup in a remote location, install the VIOS by using the available VIOS version, copy the backup data back to the VIOS after the installation, and then restore the VIOS metadata by using the viosbr -restore command.

To manually back up and restore the VIOS metadata, complete the following steps:

Back up the VIOS metadata, by using the following command:
```
viosbr -backup -file <FileName>
```
Note: You must transfer the backup file (FileName) to a remote location so that you can restore the VIOS metadata when you are in step 4. You can also back up any other data from rootvg, if required.
Install the VIOS image by using the available installation methods, such as NIM installation.
Transfer the backup file (FileName), saved in step 1, to the VIOS.
Note: Network connectivity must be available for the file transfer to succeed.
Restore the VIOS metadata, by using the following command:
```
viosbr -restore -file <FileName>
```
Note: Any other data that was backed up in step 1 can be transferred back to the VIOS , if required.