DPOD software updates 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:
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 |
11.0 |
→ 1.0. |
12. |
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 |
11. |
0 → 1.0. |
13.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 |
11. |
0 → 1.0. |
13. |
0 |
13. |
0 → 1.0. |
14.0 | 1.0. |
10. |
x → 1.0. |
13.0 |
13.0 → 1.0. |
14.0 | 1.0. |
11.0 → 1.0. |
13.0 |
13. |
0 → 1.0. |
14.0 | 1.0.12.0 |
→ 1.0. |
13.0 |
|
13. |
0 → 1.0. |
14.0 | 1.0. |
13.0 → 1.0. |
14.0 | ||
1.0. |
---|
15. |
---|
x 3 | 1.0. |
---|
9.0 → 1.0.11.0 |
13.0 |
13.0 → 1.0. |
14.0 |
14.0 → 1.0. |
15. |
x | 1.0.10. |
x → 1.0. |
13.0 |
13. |
0 → 1.0. |
14.0 |
14.0 → 1.0. |
15. |
x | 1.0. |
11.0 |
→ 1.0. |
13. |
0 |
|
13. |
0 → 1.0. |
14.0 |
14.0 → 1.0. |
15. |
x | 1.0. |
12. |
0 → 1.0. |
13.0 |
13.0 → 1.0. |
14.0 |
14.0 → 1.0. |
15. |
x | 1.0. |
13.0 → 1.0. |
14.0 |
14.0 → 1.0. |
15. |
x | 1.0. |
14. |
0 → 1.0.15.x | |
1.0. |
---|
16.0 | 1.0. |
---|
9.0 → 1.0. |
11.0 |
11.0 → 1.0.13.0 |
13.0 |
→ 1.0. |
14. |
0 |
1
14.0 |
→ 1.0. |
16.0 | 1.0. |
10. |
x → 1.0.13.0 |
14. |
0 → 1.0. |
16.0 | 1.0.11.0 → 1.0.13.0 |
14.0 → 1.0. |
16.0 | 1.0. |
12.0 → 1.0.13.0 |
14.0 → 1.0. |
16.0 | 1.0.13.0 → 1.0.14.0 |
14. |
0 → 1.0. |
16.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
...
1.0.13.0 → 1.0.14.0
1 Up to version 1.0.8.6, the fix pack file does not include previous fix packs, so each fix pack should be applied one by one.
2 Version 1.0.12.0 requires at least 1.0.10.0 because of Store engine upgrade and data upgrade issues.
3 Version 1.0.14.0 requires at least 1.0.13.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.
...
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, the cell manager Web Console will be unavailable. Do not start the 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
app-util.sh
("Start All").
Copy the Software Update Files to DPOD Server
DPOD software updates are available through IBM Fix Central. The download consists of two files:
...
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>.sfs
The md5 hash calculation of the update file:DPOD-fixpack-<version number>.md5
md5
Create necessary directories:
Code Block mkdir -p /installs/update/fix/TODO /installs/update/fix/logs
Copy the update files to the following directory on DPOD server:
/installs/update/fix/TODO
If the directory does not exist, execute the following command to create it:
Code Block language bash mkdir -p /installs/update/fix/TODO
Make Sure there is Enough Free Disk Space
...
Make Sure there is Enough Free Disk Space
Inspect the free space of each mount point. You may use the following command:
...
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 | Remove the directories |
Follow Special Steps
Some versions require special steps. Make sure to follow them:
...
Install the Software Update
Make 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
sudo
is not supported):
Code Block | ||
---|---|---|
| ||
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 |
Note |
---|
Do not interrupt the software update process after it has started. |
Please review the upgrade log 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.
...
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 | ||
---|---|---|
| ||
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:
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 -> Installation and Upgrade -> Upgrade |
Configuring the Data Migration Tool
You may edit the configuration file /installs/data-migration-tool/data-migration-tool.conf
before running the tool.
The following entries are of interest (other settings should not change unless advised otherwise by IBM support):
...
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.
...
, 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
...