Skip to main content

Striim Platform 5.0 documentation

Preparing to upgrade and exporting the metadata

Important

Before following the instructions below, read the Release notes so you will be aware of any changes that may be required to your environment or applications before or after the upgrade.Release notes

  1. Back up the cluster as described in Backing up and restoring a cluster.

  2. On each server in the cluster, copy any .jar files you have added to Striim's lib directory to another location. These should be easy to identify since the files installed by Striim all have the same date.

  3. Applications that have recovery enabled will pick up from the recovery checkpoint when they are restarted after the upgrade. In order for this to work correctly, after the upgrade they must be deployed on the same, unchanged deployment groups with the same options. Make notes as necessary to duplicate your deployment scenarios.

  4. Quiesce and undeploy all running applications with persisted streams. If upgrading from Striim 3.x, quiesce and undeploy all running applications with Spanner Writer targets. Stop and undeploy all other running and deployed applications.

  5. Open the Striim console and enter the following commands to stop the hidden monitoring applications:

    stop application Global.MonitoringSourceApp;
undeploy application Global.MonitoringSourceApp;
stop application Global.MonitoringProcessApp;
undeploy application Global.MonitoringProcessApp;
exit;

  6. On each server in the cluster, stop the striim-node process:

    • In CentOS 6 or Ubuntu 14.04:

      sudo stop striim-node

    • In CentOS 7 or Ubuntu 16.04 or later:

      sudo systemctl stop striim-node

  7. If the metadata repository is hosted on Derby, on the server where Derby is installed, stop it:

    • In CentOS 6 or Ubuntu 14.04:

      sudo stop striim-dbms

    • In CentOS 7 or Ubuntu 16.04 or later:

      sudo systemctl stop striim-dbms

  8. Export the metadata.

    If the metadata repository is hosted on Derby, on the server that hosts Derby, enter the following commands to export the metadata:

    cd /opt/striim
sudo bin/tools.sh -A export -F export.json

    If the metadata repository is hosted on Oracle, enter the following commands on any server:

    cd /opt/striim
sudo bin/tools.sh -A export -F export.json -r oracle

    If the metadata repository is hosted on PostgreSQL, enter the following commands on any server:

    cd /opt/striim
sudo bin/tools.sh -A export -F export.json -r postgres

  9. Back up the Striim configuration files to /opt/striim/conf-backup (or, if you prefer, some other directory) so it will not be removed when you uninstall the old version of Striim (sks.jks and sksKey.pwd exist only in 3.9.8 and later):

    sudo mkdir conf-backup
sudo cp conf/startUp.properties conf-backup
sudo mv conf/sks.jks conf-backup 
sudo mv conf/sksKey.pwd conf-backup

  10. If the metadata repository is hosted on Derby, skip this step. 

    Remove the old repository tables (which you backed up in step 1):

    If the metadata repository is hosted on Oracle, log in to sqlplus as the user created in Configuring Striim's metadata repository and run /opt/striim/conf/DropMetadataReposOracle.sql and /opt/striim/conf/DropMeteringReposOracle.sql.

    If the metadata repository is hosted on PostgreSQL, log in to psql as the user created in Configuring Striim's metadata repository and run /opt/striim/conf/DropMetadataReposPostgresql.sql and /opt/striim/conf/DropMeteringReposPostgres.sql.

  11. Continue with Upgrading in CentOS or Upgrading in Ubuntu.

In this section: