IriusRisk upgrade guide

This document is intended to explain how to upgrade your IriusRisk version 2 to newer versions. If your IriusRisk installation is lower than 2.0.0, you need to follow this article instead.

We strongly encourage testing on a pre-production instance first.

Perform a backup of your database

Regardless of your installation type, you should always have a backup of your IriusRisk database, especially before performing an upgrade to newer versions.

This step is mandatory if you want to be able to do a rollback later.

If you're using PostgreSQL we recommend performing a backup with pg_dump tool. The command is as follows:

pg_dump -U iriusprod -h your.database.endpoint iriusprod -Fc -f DATABASE.dump

Upgrade your IriusRisk

Docker based installations:

First of all you need to stop your running docker containers by opening a command prompt and changing to the folder that contains IriusRisk files along with docker-compose.yml and execute:

docker-compose stop

Then you need to take a look at your docker-compose.yml. There is a section where you specify the image for tomcat8 container. Check that it points at a generic version 2 for the latest updates:

image: continuumsecurity/iriusrisk-prod:tomcat8-2

"continuumsecurity/iriusrisk-prod:tomcat8-2" will always contain the latest 2.X version.

Then ensure that you have the latest docker images with:

docker-compose pull

Start up your new installation:

docker-compose up -d

If you have any custom TLS certificates, you will also need to copy them to the iriusrisk-nginx container and then restart it:

docker cp ./cert.pem iriusrisk-nginx:/etc/nginx/ssl/star_iriusrisk_com.crt
docker cp ./key.pem iriusrisk-nginx:/etc/nginx/ssl/star_iriusrisk_com.key

docker restart iriusrisk-nginx

On the first run of the new IriusRisk release there will be upgrades and migrations performed on the database. This process can take more than 30 minutes depending on your database size and the type of migrations. You can check the progress of this by viewing the container console with:

docker logs -f iriusrisk-tomcat8

The system is up and running and available for use once you see this message:

INFO [main] org.apache.catalina.startup.Catalina.start Server startup in xxxxxx ms 

WAR based installations:

You can find the latest war binaries here.

We strongly encourage testing on a pre-production instance first.

These are the recommended steps:

1. Do a database backup with the steps mentioned before
2. Copy the old WAR file as a backup (to rollback in case you need it).
3. Copy the new war on tomcat webapps folder. Be sure that you rename it correctly.
4. When you start the application, check the catalina logs to ensure tomcat is deploying the new war.
5. There may be migrations and the upgrade process can be long depending on the data. You can check out the activity in the catalina log file.