...
You should consider full backup.
Obtain the software update
DPOD software updates are available through IBM fix central.
...
- The update file in the format of : DPOD-fixpack-<version number>.sfs (for example: DPOD-fixpack-1_0_9.sfs)
- The md5 hash calculation of the update file : DPOD-update-<version number>.md5
Copy the software update to the DPOD server
Copy the update files to the following directory on the DPOD server :
...
Code Block | ||
---|---|---|
| ||
mkdir -p /installs/update/fix/TODO |
Install the software update
Run the following command from the location you downloaded the update files to.
...
Code Block | ||
---|---|---|
| ||
MonTierUpdateInstaller.sh -u DPOD-update-1_0_9.sfs -s DPOD-update-1_0_9.md5 |
Data Migration Tool
The upgrade process checks the existence of Store indices that were created in early versions of the product.
In case that early version indices exist, the upgrade process will stop and notify you of a manual step that you will need to run :
Code Block | ||
---|---|---|
| ||
Some of the stored application data cannot be migrated to the latest version of the Store service. A data migration tool has been deployed in /installs/data-migration-tool. You may run it using the following command: /installs/data-migration-tool/data-migration-tool.sh Further information can be found in the documentation at: Admin Guide -> Installation and Upgrade -> Upgrade -> Upgrade to 1v1.0.109.0 - Special Steps |
Configuring the Data Migration Tool
You may edit the configuration file /installs/data-migration-tool/data-migration-tool.conf before running the tool. There are two entries of interest:
- 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. - delete.kibana_indices (default: true) - determined 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 and migrate Kibana indices to the new store version - however Kibana version that comes with DPOD 1.0.9.0 is unable to read the old indices format, so it is up to you to fix the indices manually according to Kibana's documentation. - Leave the other settings in data-migration-tool.conf as they are, unless advised otherwise by support.
Running the Data Migration Tool
To run the data migration tool manually:
...
Code Block | ||
---|---|---|
| ||
Data migration tool finished successfully |
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 migrated 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.
Resuming Software Update
To proceed with the software update, you can rerun the software update command:
...
Please review the upgrade log file if the console displays any error messages.
Update Store Allocation
Open the DPOD admin console on your favorite browser:
...