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

The following sections describe the process of upgrading an existing installation.

Cumulative Upgrade

Up to version 1.0.8.6, each DPOD fix pack file does not include previous fix packs. For example, in order to upgrade from 1.0.7.0 to 1.0.8.6:

• First upgrade to 1.0.8.0 with the 1.0.8.0 fix pack file.
• Then upgrade to 1.0.8.6 with the 1.0.8.6 fix pack file.

From version 1.0.8.6 and above, the latest fix pack in Fix Central includes all previous fix packs above 1.0.8.6. For example, in order to upgrade from 1.0.8.0 to 1.0.10.0:

• First upgrade to 1.0.8.6 with the 1.0.8.6 fix pack file.
• Then upgrade to 1.0.10.0 with the 1.0.10.0 fix pack file, which includes both 1.0.9.0 and 1.0.10.0.

Upgrading Cell Environment

To upgrade a Cell environment - first stop DPOD on the Cell Manager and on all Cell Members, then upgrade the Cell Members, and only after all Cell Members have been upgraded, upgrade the Cell Manager.

...

Upgrade Paths

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.

² Version 1.0.14.0 requires at least 1.0.13.0 because of an architecture change of the Store engine.

³ 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

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.

...

1. The download consists of two

...

1. files:

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

   (for example: DPOD-fixpack-1_0_8_5.sfs)

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

   .md5 (for example: DPOD-fixpack-1_0_8_5

   1. .md5

   )

Ensure squashfs Support (only for Non Appliance Installation)

...

Copy the Software Update to DPOD Server

...

2. Create necessary directories:

   Code Block

...

...

lsmod | grep squash

expected output :
squashfs              

...

1. mkdir -p /installs/update/fix/TODO /installs/update/fix/logs

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

...

1. /installs/update/fix/TODO

...

mkdir -p /installs/update/fix/TODO

Make Sure there is Enough Free Disk Space

Root ("/") Mount Point Free Space

The root ("/") mount point requires at least 100MB free space.

Installs ("/installs") Mount Point Free Space

The "/installs" mount point free space can be displayed using Inspect the free space of each mount point. You may use the following command:

df -h /installs

Output example:
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/vg_inst-lv_inst  7.0G  5.5G  1.6G  79% /installs

During the software update installation, the internal configuration database is being backed-up. The backup requires additional available disk space on the "/installs" mount point.

To calculate the needed available disk space for the internal configuration database backup please use the following command (in this example DB size is 43MB):

du -ksh /app/derby/

Output example:
43M     /app/derby/

See the following table for required available disk space on "/installs" for the software update:

...

The following table lists the required available space:

If there is not enough free space on the /installs mount point, you may free some from the following directories:

Follow Special Steps

Some versions require special steps. Make sure to follow them:

Install the Software Update

Run the following command from the location you downloaded the update files to:

...

1. If this DPOD server is an all-in-one or a cell manager, make sure DPOD is up and running, and that the Store status is green (under DPOD Health → Store). Upgrading is possible only if the current installation is healthy.

2. Execute the following commands as root (using sudo is not supported):

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

For example:
MonTierUpdateInstaller.sh -u DPOD-updatefixpack-1_30_16_0.sfs -s DPOD-updatefixpack-1_30_16_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.

Optional Manual Steps during Software Update

Some versions require manual steps in order to complete the upgrade. These steps are described below.

Rerunning the Installer after Installer Update

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.
INFO
importantImportant !!! Please run MonTierUpdateInstaller.sh again.

This message means that the MonTierUpdateInstaller.sh was updated and you should rerun the command.
After running the command again you will be prompted to confirm the software update process. press "Y" to confirm or "N" to abort.

...

the software update installer again.

Rerunning the Installer after Operating System Update

Some versions upgrade the operating system (CentOS) when DPOD is installed in Appliance Mode.

In that case, the installer should be rerun manually after the OS upgrade is complete and the server is restarted.

Running Store Data Migration Tool

Some versions include new versions of the Store engine, which might require some of the existing data to be migrated to a newer format or structure.

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

Configuring the Data Migration Tool

You may edit the configuration file /installs/data-migration-tool/data-migration-tool.conf before running the tool, and change the following entry:

• duration.limit (default: 999999) - limits the execution time in minutes.
  This option is useful if you want to schedule the tool to run during off-peak time.
  In such a case, you can limit the tool to run for a few hours each time and schedule it to start when off-peak time starts, so performance will not be impacted during peak time hours.

Running the Data Migration Tool

1. Make sure DPOD is up and running. The data migration tool is designed to work while DPOD is up and running, so users may sign in to DPOD and use it while the data migration tool is upgrading the data in the background.

2. Since the tool is a long-running process, it is recommended to run it in a "no hang-up" mode, which will cause the process to continue running even after the SSH session is closed. In this mode, the console output is written to nohup.log file in the local directory. Use the following command to run the tool and inspect the console output:

   Code Block
   language bash
   nohup /installs/data-migration-tool/data-migration-tool.sh & tail -f nohup.out

3. The data migration process may take anywhere between a few minutes and a few days, depending on the amount of data, the server load and the server hardware. A rough estimation of the time left will be presented while the process is running.

4. Please review the data migration tool log file (/installs/logs/store_data_migration.log) if the console displays any error message.

Interrupting the Data Migration Tool

Pressing Ctrl+C or setting duration.limit in the configuration file will stop the tool during the migration process.

Stopping the tool will cause it to re-process the last index that was in the middle of the migration on the next run.

While this is usually not an issue, note that on some cases it may cause complications, for example:

1. The user wants the tool to run during a nightly maintenance window, between 2-4 AM.

2. The tool is scheduled using cron to 2 AM and the duration.limit setting is set to 120 minutes.

3. For this specific user, depending on its hardware and data sizes, processing of each index takes about 3 hours.

4. Since the tool is interrupted after 2 hours, on the next night, the tool will try to migrate the same index again and will never advance to the next index.