DPOD software updates DPOD software upgrades are available from time to time and include enhancements, security updates, component upgrade, bug fixes, etc.

...

The following table describes the upgrade paths between versions:

...

...

¹ Version 1.0.12.0 requires at least 1.0.10.x because of Store engine upgrade and data upgrade issues.

^{3 2} Version 1.0.14.0 requires at least 1.0.13.0 because of an architecture change of the Store engine.

^{4 3} Version 1.0.15.0 requires at least 1.0.14.0 because of an architecture change of the Store engine.

Upgrading a Cell Environment

Note: This procedure has changed since 1.0.12.0. In previous versions the process of upgrading a cell environment was different.

...

To upgrade a cellenvironment:

1. Make sure the entire cell is up and running. Upgrading is possible only if the cell is healthy.

2. Upgrade the cell manager.
   When the cell manager upgrade is complete, only the following services should be up and running - MonTier-Derby, MonTier-es-raw-trans-Node-1/2/3/4 (the Web Console will be unavailable).
   Do not start the other services manually on the cell manager unless requested explicitly.

3. Upgrade all cell members (can be done in parallel).

4. When the cell members upgrade is complete, start the cell manager services using the app-util.sh ("Start All").

...

Backup the Servers

It is highly recommended to perform a full backup (including the operating system) of all DPOD servers prior to upgrading, so the system can be restored in case of a failed upgrade.

In virtual environments, it is highly recommended to create snapshots of the virtual machines, which can be removed later once the upgrade is completed successfully.

Copy the Software Update Files to DPOD Server

1. DPOD software updates are available through IBM Fix Central. The download consists of two files:

   1. The update file: DPOD-fixpack-<version number>.sfs

   2. The md5 hash calculation of the update file: DPOD-fixpack-<version number>.md5

2. Copy the update files to the following directory on DPOD server: Create necessary directories:

   Code Block
   mkdir -p /installs/update/fix/TODO /installs/update/fix/

   TODO

   logs

   If the directory does not exist, execute the following command to create it:

3. Code Block

   language	bash

   mkdir -p

   Copy the update files to the following directory on DPOD server: /installs/update/fix/TODO

Make Sure there is Enough Free Disk Space

...

...

cd /installs/update/fix/TODO
MonTierUpdateInstaller.sh -u DPOD-fixpack-<version number>.sfs -s DPOD-fixpack-<version number>.md5

For example:
MonTierUpdateInstaller.sh -u DPOD-fixpack-1_0_1416_0.sfs -s DPOD-fixpack-1_0_1416_0.md5

If SSH connection is lost during upgrade, the upgrade will continue. reconnect to the server and check the log files for the process status and outcome.

Please review the upgrade log file if the console displays any error messages.

...

Some versions make changes to the installer file itself (MonTierUpdateInstaller.sh). In that case, the following message will be displayed, and the installer should be rerun manually:

Found new version of the software update installer... updating
Software update installer was updated successfully.

Important !!! Please run the software update installer again.

...

If the upgrade process detects data that should be migrated before applying the upgrade, the following message will be displayed, and the data migration tool should be run manually:

Some of the existing data needs to be migrated to a newer format or structure.
The data migration tool has been deployed in /installs/data-migration-tool.
Further information can be found in the documentation at: Admin Guide -> Upgrade -> Upgrade

Configuring the Data Migration Tool

...