IMPORTANT: Before any upgrade, make sure to create a backup image. There is no way to revert to the previous state if anything goes wrong during the upgrade and you will lose all your data.
In this example, we will perform an upgrade from version 221 to 229. Since we can skip only one version during the upgrade, our path will be: 221 -> 225-3 (latest version of 225) -> 229-2 (latest version of 229)
To check on which version you are currently, and to which version you should upgrade, please run the following command:
yum --showduplicates list instana-console
This will show you the list of all available instana-console versions and highlight your current version:
Make sure to perform the upgrade as a root user on all host instances (sudo su).
First, we need to upgrade the ClickHouse instance (host):
- run instana stop
- run instana images prune
(this will remove all containers from the local cache that are no longer required for the current version). - navigate to the folder where your settings.hcl file is (find ./ -name settings.hcl)
- run yum install instana-console-225-3
- run instana update
- run docker ps, after the upgrade has finished, check if all containers are up and healthy.
After we finish the upgrade on the ClickHouse instance, we can proceed to the Dual-host instance.
On Dual-host instance (host):
- run instana stop
- run instana images prune
(this will remove all containers from the local cache that are no longer required for the current version). - navigate to the folder where your settings.hcl file is (find ./ -name settings.hcl)
- run yum install instana-console-225-3
- run instana update
- run docker ps, after the upgrade has finished, check if all containers are up and healthy.
If the upgrade to version 225-3 was successful and both instances are running normally, we can proceed to upgrade to the 229-2 version (in this situation, the latest Instana backend version).
We will repeat the process and upgrade to the 229-2 Instana version.
IMPORTANT: Once again, before any upgrade, make sure to create a backup image. There is no way to revert to the previous state if anything goes wrong during the upgrade and you will lose all your data.
First, need to upgrade the ClickHouse instance (host):
- run instana stop
- run instana images prune
(this will remove all containers from the local cache that are no longer required for the current version). - navigate to the folder where your settings.hcl file is (find ./ -name settings.hcl)
- run yum install instana-console-229-2
- run instana update
- run docker ps, after the upgrade has finished, check if all containers are up and healthy.
After we finish the upgrade on the ClickHouse instance, we can proceed to the Dual-host instance.
On Dual-host instance (host):
- run instana stop
- run instana images prune
(this will remove all containers from the local cache that are no longer required for the current version). - navigate to the folder where your settings.hcl file is (find ./ -name settings.hcl)
- run yum install instana-console-229-2
- run instana update
- run docker ps, after the upgrade has finished, check if all containers are up and healthy.
In case something goes wrong during the upgrade, create a support ticket and our Instana Support Team will provide additional help.
Comments