Upgrade the On-Premises CR Server

To upgrade the On-Premises Continuous Reliability (CR) Server (Backend):

1. Download the latest tarball for the version you have installed.

   https://s3.amazonaws.com/app-takipi-com/deploy/takipi-server/takipi-server-java.tar.gz

📘

Container Images

For our official container images, please visit https://hub.docker.com/u/overops

2. Take Backups of

• bin/server-envs.sh

• conf/tomcat/shared/*

  DB Drivers
  Make a backup of your DB drivers which would be located in
  <TAKIPI_SERVER_HOME>/tomcat/webapps/ROOT/WEB-INF/lib/

3. Stop the collector(s).
4. Stop the OverOps backend
5. Check which services are currently running and then stop the server using

📘

TAKIPI_SERVER_HOME

OverOps is by default installed in
/opt/takipi-server

cd <TAKIPI_SERVER_HOME>/bin
./takipi-server.sh stop

6. Verify that all OverOps related services (JVMs), such as Dynalite, H2, Tomcat, etc., are stopped.

📘

Note

If you're using a database like MySql or Postgres H2 will not be running.

🚧

Note

If you're using a database like MySql or Oracle install updated JDBC drivers.
Instructions to install JDBC drivers here

7. Make a backup of the server directory.

8. Remove the content of the following directory to ensure the lastest JAR files are loaded

rm <TAKIPI_SERVER_HOME>/tomcat/webapps/ROOT/WEB-INF/lib/*

9. Untar the new version over the old one.
   The command below assumes that the takipi-server is installed in the
   /opt directory.

tar -zxvf takipi-server-java.tar.gz -C /opt

❗️

Important

Verify that you're not extracting the tar into /opt/takipi-server but actually overwriting takipi-server by extracting to /opt.
You might want to extract the tar first to a tmp folder.

🚧

Owner and Permissions

Ensure that the Owner and Permissions are set correctly

10. Copy your database drivers back into the ROOT/WEB-INF/lib directory above
    The drivers are typically named as follows:

11. Optional Compare the differences between your backup and the new files in the conf directory ( smtp.properties, smtpserver.properties, etc.).
12. Start the OverOps backend.

❗️

Upgrading from a Version Prior to V4.31

MySQL SSL data connections
Data connections to MySQL via SSL are enabled by default starting with Version 4.31.
If you have not enabled SSL for MySQL in your previous version you will need to disable SSL data connections for MySQL.
To disable data connections via SSL add the --no-db-ssl startup argument flag to the takipi-server startup.
This will update the configuration file and make SSL disabled persistent for future server restarts. To enable SSL use the --db-ssl flag to turn SSL on.

The options:

--db-ssl       to enable
--no-db-ssl    to disable

Example
./takipi-server.sh start -u <The host name or IP address of the server> --db-no-ssl

./takipi-server.sh start -u <The host name or IP address of the server>

13. Validate that the backend comes up and that you can log in to your server.
14. Start the collectors.
15. Validate and test that your backend is processing data correctly.