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

...

Upgrading a Cell Environment

To upgrade a cell environment:

1. Make sure the entire cell is up and running. Upgrading is possible only if the cell is healthy.
2. Upgrade the cell manager.
3. 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.
4. Upgrade all cell members (can be done in parallel).
5. 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

...

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

Follow Special Steps

...

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):

1. 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.
2. delete.kibana_indices (default: true) - determines whether Kibana indices should be deleted or not.
   true - Delete old Kibana indices - all exiting Kibana dashboards and other settings will be deleted.
   false - Keep Kibana indices and try to migrate them to the new store engine version - however, it is up to you to fix the indices manually according to Kibana's documentation.

...

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:

   Code Block
   language bash theme RDark
   nohup /installs/data-migration-tool/data-migration-tool.sh &

   
   

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 if the console displays any error message.

...