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.
Upgrade Paths
The following table describes the upgrade paths between versions:
From | 1.0.9.0 | 1.0.10.x | 1.0.11.0 | 1.0.12.0 | 1.0.13.0 | 1.0.14.0 | 1.0.15.x |
|---|---|---|---|---|---|---|---|
1.0.10.x | 1.0.9.0 → 1.0.10.x | ||||||
1.0.11.0 | 1.0.9.0 → 1.0.11.0 | 1.0.10.x → 1.0.11.0 | |||||
1.0.12.0 1 | 1.0.9.0 → 1.0.11.0 | 1.0.10.x → 1.0.12.0 | 1.0.11.0 → 1.0.12.0 | ||||
1.0.13.0 | 1.0.9.0 → 1.0.11.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | |||
1.0.14.0 2 | 1.0.9.0 → 1.0.11.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 | ||
1.0.15.x 3 | 1.0.9.0 → 1.0.11.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 | 1.0.14.0 → 1.0.15. |
...
Up to version 1.0.8.0, each DPOD fix pack file is not including any previous fix pack. For example: to upgrade from v1.0.5 to v1.0.7 you will need to first upgrade to v1.0.6 with the downloaded fix of v106 and after a successful upgrade to v106 you may apply the fix to v107.
DPOD installation from version 1.0.8.0 and above can apply the latest fix available in fix central. For example: to upgrade from v1.0.7 to latest you will need to first upgrade to v1.0.8 with the downloaded fix of v108 and after a successful upgrade apply the latest fix from fix central.
The following sections describe the process of upgrading an existing installation.
| Note |
|---|
To upgrade cell environment - stop DPOD on the cell manager and on all cell members, and then run the following steps for each server separately, first for each cell member and only after for the cell manager |
...
x | |||||||
1.0.16.0 | 1.0.9.0 → 1.0.11.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 | 1.0.14.0 → 1.0.16.0 | 1.0.15.x → 1.0.16.0 |
|---|
1 Version 1.0.12.0 requires at least 1.0.10.x because of Store engine upgrade and data upgrade issues.
2 Version 1.0.14.0 requires at least 1.0.13.0 because of an architecture change of the Store engine.
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
To upgrade a cellenvironment:
Make sure the entire cell is up and running. Upgrading is possible only if the cell is healthy.
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.Upgrade all cell members (can be done in parallel).
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
DPOD software updates are available through IBM
...
Fix Central.
...
The download consists of two
...
files:
The update file
:
DPOD-fixpack-<version number>.sfs
The md5 hash calculation of the update file:
DPOD-fixpack-<version number>.md5
Make Sure squashfs support (only for Non Appliance Installation )
Make sure the update file can be mounted ( squashfs support) using the following command
| Code Block | ||
|---|---|---|
| ||
lsmod | grep squash
expected output :
squashfs |
Create necessary directories:
Code Block mkdir -p /installs/update/fix/TODO /installs/update/fix/logsCopy the update files to the following directory on
...
DPOD server:
...
| theme | RDark |
|---|
/installs/update/fix/TODO
If the directory is missing for some reason, please re create it :
| Code Block | ||
|---|---|---|
| ||
mkdir -p /installs/update/fix/TODO |
Make sure there is enough disk space
The software update requirements for available disk space may change from version to version. See version table below.
...
Make Sure there is Enough Free Disk Space
Inspect the free space of each mount point. You may use the following command:
| Code Block | ||
|---|---|---|
| ||
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):
| Code Block | ||
|---|---|---|
| ||
du -ksh /app/derby/
Output example:
43M /app/derby/ |
See the following table for needed available disk space on "/installs" for the software update:
...
The following table lists the required available space:
Mount Point | Required Available Space |
|---|---|
/ | 100 MB |
/installs | 4 GB + internal configuration database size |
If there is not enough free space on the /installs mount point, you may free some from the following directories:
Directory | Description |
|---|---|
/installs/update/fix/TODO | Remove old DPOD update files (.sfs) |
/installs/backups |
Move old DPOD backup directories to a different server. It is recommended not to delete the backups until you are absolutely sure you don’t need them anymore. |
/installs/APPL-setup |
Install the software update
| Note |
|---|
A technical issue prevents upgrading DPOD installations that were installed using version 1.0.2.0 ISO file. To identify the ISO version used for your installation, please run the CLI Admin utility (app-util.sh) and select option 9 (system version). |
Run the following command from the location you downloaded the update files to.
...
| theme | RDark |
|---|
| Remove the directories |
Follow Special Steps
Some versions require special steps. Make sure to follow them:
| Child pages (Children Display) |
|---|
Install the Software Update
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.
Execute the following commands as root (using
sudois not supported):
| Code Block | ||
|---|---|---|
| ||
cd /installs/update/fix/TODO MonTierUpdateInstaller.sh -u DPOD-updatefixpack-<version number>.sfs -s DPOD-updatefixpack-<version number>.md5 For example: |
...
| Code Block | ||
|---|---|---|
| ||
MonTierUpdateInstaller.sh -u DPOD-updatefixpack-1_0_316_0.sfs -s DPOD-updatefixpack-1_30_16_0.md5 |
...
| Note |
|---|
Do not interrupt the software update process after it has started. |
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:
| Code Block | ||||
|---|---|---|---|---|
| INFO file MonTierUpdateInstaller.sh
| |||
Found new version of the software update installer... updating Software update installer was updated successfully. INFO importantImportant !!! Please run MonTierUpdateInstaller.sh the software update installer 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.
| Code Block | ||
|---|---|---|
| ||
Software update :
Please DO NOT interrupt during the process !
Are you sure you want to continue ? [y/n] |
When the software update level is not compatible with the current system version you will receive the following message on the console output :
| Code Block | ||
|---|---|---|
| ||
error, software update can NOT be applied to this system version. aborting update... |
| Note |
|---|
Do Not interrupt the software update process after it has begun |
...
| Code Block | ||
|---|---|---|
| ||
Starting software update. log file is /installs/update/fix/logs/montier-update-2016-08-01_16-13-35.log
stopping application ...
application stopped successfully.
starting software update.....
updated complete successfully
starting application ...
application strated successfully.
update DPOD-update-1_3_0.sfs was installed successfully. log file /installs/update/fix/logs/montier-update-2016-08-01_16-13-35.log |
Please review the upgrade log file if the console displays any error messages.
Manual Post Update Installation
...
Important: After the upgrade is complete, Syslog must be manually re-configured on all monitored devices using the Web Console (under Manage → Monitored Devices).
...
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:
| Code Block | ||
|---|---|---|
| ||
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
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.
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.logfile 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.outThe 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.
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:
The user wants the tool to run during a nightly maintenance window, between 2-4 AM.
The tool is scheduled using cron to 2 AM and the
duration.limitsetting is set to 120 minutes.For this specific user, depending on its hardware and data sizes, processing of each index takes about 3 hours.
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.