Please follow the steps shown in Kiuwan On-Premises Installation Guide - Upgrading your KOP installation in order to upgrade.
Once the upgrade is completed, you should see this versions in the KOP system administration console:
Step 2: stop the old Kiuwan On-Premises server
First, make sure there are no running analysis before stopping the application server. You can check this in the sysadmin console:
If you are using an automation tool to launch Kiuwan analysis, make sure you pause the needed jobs so no more analysis analyses enter the Kiuwan queues.
Once there are no more active analyses, you should wait for Redis queues to be completely freed before stopping the Kiuwan server. This should take up to 30 minutes maximum.
To stop the running Kiuwan and prevent creating more data before backuping it up, run this these commands in the Kiuwan On-Premises host.:
docker exec -it [kiuwan_on_premise_container_name] /bin/bash supervisorctl stop wildfly exit
Using mysqldump or MySQL Workbench (using self-contained file is recommended), backup these schemas data and structure structure schemas:
Access your persisten persistent volume and backup central and source code repositories, located in:
Follow the steps provided in the Kiuwan On-Premises Installation Guide to prepare your the new installation of Kiuwan On-Premises new installation , but do NOT perform the installation step (that may be executing install.sh or other scripts depending on your installation needs).
Step 7: restore the database
Restore the mysql MySQL backup, either using mysqldump or MySQL Workbench restore utility (import from self-contained file is recommended).
This last step forces Kiuwan On-Premises to be updated update to the current version (the one tied to the used kiuwan-cluster distribution). Execute in your new Kiuwan host console:
Step 9: check your data and discard the old installation
Once the Kiuwan On-Premises servers are up, you can access your new installation using the same users username and passwords password and all the previous data will be there.
- The database backup and restore process were completed successfully.
- You have correctly backuped backed up and restored the repository data.