You can migrate Paragon Insights Release 3.2.0
(Docker Compose installation) to Paragon Insights Release 4.0.0.
Since Paragon Insights Release 4.0.0 does not support a Docker
Compose based installation, you can only migrate (and not upgrade)
from a Release 3.2.0 Docker Compose installation to Release 4.0.0.
Note: Config/Data/User/Helper files
must be migrated from Paragon Insights Release 3.2.0 Docker Compose
installation to Paragon Insights Release 4.0.0.
For more information on upgrade that is not Docker Compose related,
see Upgrading Paragon Insights Release 3.X with Kubernetes-based Installation to Release 4.X.
Follow these steps to upgrade to Paragon Insights Release
4.0.0:
- Backup Config data.
The Config files must be backed up in a folder other than /var/local/healthbot/ to avoid losing data during uninstallation.
- Backup configuration and helper files.
- Backup Times Series Database (TSDB) data.
- Backup Keycloak users.
You backup Keycloak users when you are migrating existing users
to the new IAM service in Paragon Insights Release 4.0.0. However,
you can skip this step if user migration is not required.
To backup Keycloak users:
Backup the keycloak-hb.json file.
Run the following command to identify the keycloak container
ID in the namespace.
root@linux $ docker ps | grep keycloak
For steps 1.c.iii through 1.c.v, replace <keycloak
docker-container id> with the Keycloak container
ID that you identified.
Connect to the keycloak container.
root@linux $ docker exec -it <keycloak docker-container id> bash
Run the following command from the keycloak container
to generate the backup file.
root@linux $ docker exec -it <keycloak docker-container id> bash
root@67dfd489d4 # /opt/jboss/keycloak/bin/standalone.sh -Dkeycloak.migration.action=export -Dkeycloak.migration.provider=singleFile -Dkeycloak.migration.file=/tmp/keycloak-hb.json -Djboss.socket.binding.port-offset=999 -Dkeycloak.migration.realmName=healthbot
Terminate the process using ctrl-c after you receive the following message:
Keycloak 9.0.0 (WildFly Core 10.0.3.Final) started in 17548ms - Started 590 of 885 services (601 services are lazy, passive or on-demand)
Disconnect from the keycloak container
and copy the file from the keycloak container to your local system.
root@linux $ docker cp <Keycloak docker-container id>:/tmp/keycloak-hb.json /root/backup/keycloak-hb.json
The backup process is not complete. The backed up data is stored
in the host machine.
- Uninstall Paragon Insights Release 3.2.0.
"yum remove <package-name>"/apt-get remove <package-name>
- Install Paragon Insights Release 4.0.0.
- Restore TSDB backup.
root@linux $ healthbot k exec -it svc/tsdb-shim "mkdir /tmp/userBackups"
root@linux $ healthbot -v tsdb restore --all --path <tsdb_backup_path>
- Migrate keyckoak users to IAM users.
- Log in to the Paragon Insights graphical user interface
(GUI) using the credentials: Username: admin,
Password: Admin123!.
When you enter these one-time credentials, Paragon Insights
prompts you to change the password. The default password for users
other than the admin user is Change123!.
- If you are the admin user, you can import user configuration
to Paragon Insights Release 4.0.0 by running the following command:
/var/local/healthbot/healthbot migrate-user -f <keycloak-backup-filename> -u <administrative-username> -p <password>
<password>
- Restore configuration and helper files.
