Applies to: Kyvos Enterprise  Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace

Kyvos Azure Marketplace   Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)

This section provides information to upgrade and rollback Kyvos Manager. 

• Upgrade Kyvos Manager from the portal 

• Rollback Kyvos Manager

Pre-upgrade verification  

Important for RHEL 8.6 and TLS

Please make sure you have moved or renamed the openssl.cnf file placed at /etc/pki/tls/ location only on Kyvos Manager and the node where Postgres Service is running to another location.

Creating backup

To upgrade the Kyvos Manager to a newer version, you must first create a backup of your existing Kyvos Manager environment.

To create a backup for the Kyvos Manager data, perform the following steps.

1. Log in to Kyvos Manager machine through the terminal.

2. Navigate to the Kyvos Manager installation path.

3. Stop the Kyvos Manager process using the command:
   ./kyvosmanager/bin/stop-km.sh 

4. Identify the location for the used kyvosmanagerdata  folder. For this, check the value of KM_DATA_DIR in the set env.sh  file in the bin folder.
   This folder contains the Kyvos Manager data including the repository.

5. Go to parent folder of the kyvosmanagerdata  folder and run the command.
   tar -zcvf file_name.tar.gz kyvosmanagerdata
   Here  file_name  is the user backup file name for the Kyvos Manager.

6. Copy the backup file to the local machine.

7. Rename your current  repo  folder at the  kyvosmanagerdata/server location, such as repo_<oldversion number>. For example, you can name it repo_2020.5.

Upgrade Kyvos Manager from the portal

1. On the navigation pane, click Application Update > Upgrade.

2. On the Upgrade Kyvos Manager page, provide the information as:

3. To see upgrade history, click the Actions menu (...) and select the View History option.

Manually upgrading Kyvos Manager

To upgrade Kyvos to a new version, perform the following steps.

1. If not stopped already, stop Kyvos Manager from the terminal using the following command.

   ./kyvosmanager/bin/stop-km.sh 

2. Copy the new Kyvos Manager setup on the machine parallel to the older version of Kyvos Manager is installed.
   For this: 

   1. Log in to the machine using the credentials of the user, which were used for installing the previous version.

   2. Download the setup from the FTP site to the location where you need to install it. For example, /data/kyvosXXXX.YY/

   3. For the older version of Kyvos Manager, we assume:

      1. Installation directory is located at /data/kyvos

      2. Kyvos Manager home directory is located at /data/kyvos/kyvosmanager

      3. Data directory is located at /data/kyvos/kyvosmanagerdata

3. Extract the Kyvos Manager bundle using the following command:
   tar -xvf KyvosManager<version>_ux64.tar.gz
   You will get a folder named kyvosmanager_war.

4. Make the following configurations in the setenv.sh file located at $KM_HOME/kyvosmanager_war/kyvosmanager/bin/

   1. Set absolute paths for the following variables, as shown in the examples.

      1. KM_BASE_DIR: Should point to the kyvosmanager_war folder.

      2. KM_DATA_DIR: Should point to kyvosmanagerdata folder of the older installation.
         Example: KM_DATA_DIR=/data/kyvosmanager_war/kyvosmanagerdata/

      3. JRE_HOME: Should point to the JRE folder in the kayvosmanager_war folder.
         Example: /data/kyvosmanager_war/jre/

5. Copy all the contents of the kyvosmanager_war/kyvosmanagerdata/server/repo/ folder to the KM_DATA_DIR/server/ location.

6. Merge the contents of your existing conf/kyvosanager.properties file to the conf/kyvosanager.properties of the new version.

7. Copy the contents of the kyvosmanager_war/kyvosmanagerdata/server/repo/ folder to the KM_DATA_DIR/server/ location.

8. Start Kyvos Manager from the terminal using the command:

   cd      

   ^{kyvosmanager_war/kyvosmanager/bin}

   ^{./start-km.sh}

9. Login to Kyvos Manager and check the version from the About page to verify a successful upgrade.

10. The Kyvos Manager cluster dashboard displays a warning message, prompting you to upgrade your Kyvos version. Click Upgrade. Now you can upgrade Kyvos .

Kyvos Manager Tomcat Server logs 

Upgrade Kyvos Manager in Azure

Post-upgrade steps

Post upgrade steps for upgrading to 2023.2 from 2023.1.x

Redeploying Zookeeper

If you're currently using the default Zookeeper on the Kyvos Manager node, you'll need to redeploy the ZooKeeper. This applies to any cluster deployed before the managed Zookeeper implementation and still uses the default Zookeeper on the Kyvos Manager node.

• For Kyvos Manager: If you are upgrading only Kyvos Manager, it is necessary to redeploy Zookeeper immediately after the upgrade.

• For Kyvos: If you are upgrading both Kyvos Manager and Kyvos using either the single click upgrade or the All components upgrade, you must redeploy Zookeeper after upgrading Kyvos Manager.

Upgrading Zookeeper for Kyvos 2023.2

1. Log onto the Kyvos Manager and navigate to Kyvos and Ecosystem > Zookeeper .

2. Here, select the External option and click the Save It will undeploy Zookeeper.

3. Once Zookeeper undeployment is complete, select the Managed by Kyvos option and click the Save This will trigger the deploy Zookeeper operation.  

4. Once Zookeeper deployment is complete, restart all Kyvos services from the Dashboard.

Switching to the previous version of Zookeeper

To access the previous version of the Zookeeper, perform the following steps. 

1. Add the previous Zookeeper version bundle to the Kyvos Manager repository at  kyvosmanagerdata/server/repo/ .

2. Take a backup of the new version 3.7.1 bundle of Zookeeper at a different location outside the Kyvos Manager repo. This bundle will be necessary for switching to the new version 3.7.1 of Zookeeper.

3. Update the previous version bundle name in the supportedBundles present in the kyvosmanagerdata/server/repo/metadata.Kyvos/zookeeper.json file by deleting the new zookeeper version bundle name and then redeploy the Zookeeper to restore managed Zookeeper to version 3.6.1.
   For example, to switch to Zookeeper version 3.6.1, before uninstalling the Zookeeper, a key having a value like supportedBundles : [zookeeper-3.7.1.tar.gz] must be updated with supportedBundles : [zookeeper-3.6.1.tar.gz]

Switching to the default non-managed version of Zookeeper

To restore the default non-managed version of Zookeeper on the Kyvos Manager node, which was removed during the uninstallation of Managed Zookeeper, you will need to manually install Zookeeper on the Kyvos Manager node.

Upgrade Graviton JRE for AWS cluster 

To upgrade the Graviton JRE version, perform the following post-upgrade steps. 

1. Create a fresh automated Graviton-based AWS cluster on the Kyvos 2023.1.1 release that contains Kyvos Manager JRE version as  Corretto-8.362.08.1

2. Upgrade Kyvos Manager to Kyvos 2023.2, which contains Kyvos Manager JRE version as  Corretto-17.0.7.7.1. 

3. Execute the following command to download the  JRE 17.0.7.7.1
   curl -o manual_node_creation_graviton_prereq.tar.gz https://s3.amazonaws.com/us-east-1.kyvos/2023.2/latest/prereq/manual_node_creation_graviton_prereq.tar.gz

4. Delete the JRE that is already existing in the following path: 
   For example, /data/kyvos/installs/kyvosmanager_releases/KyvosManager2023.2War_ux64/kyvosmanager_war/jre/

5. Untar the downloaded tar file and place it on the following path of the Kyvos Manager node:   
   For example,  /data/kyvos/installs/kyvosmanager_releases/KyvosManager2023.2War_ux64/kyvosmanager_war/jre/

6. Start the Kyvos Manager services from the following path.
   For example,  /data/kyvos/installs/kyvosmanager_releases/KyvosManager2023.2War_ux64/kyvosmanager_war/kyvosmanager/bin

7. After completing the steps, the Kyvos Manager application will be up and running. 

Rollback Kyvos Manager 

You can only roll back to an older version of the Kyvos Manager using manual steps, as there is no rollback option for the Kyvos Manager on the UI.

To roll back to a previous version, perform the following steps. 

Create a backup for the Kyvos Manager data, and perform the following steps.

1. Log in to the Kyvos Manager machine through the terminal.

2. Navigate to the Kyvos Manager installation path.

3. Stop the Kyvos Manager process using the command:
   ./kyvosmanager_war/kyvosmanager/bin/stop-km.sh 

4. Identify the location for the used kyvosmanagerdata  folder. For this, check the value of KM_DATA_DIR  in the set env.sh  file in the  bin  folder.
   This folder contains the Kyvos Manager data, including the repository.

5. Go to the parent folder of the kyvosmanagerdata  folder and run the command.
   tar -zcvf file_name.tar.gz kyvosmanagerdata
   Here  file_name  is the user backup file name for the Kyvos Manager.

6. Copy the backup file to the local machine.

7. Rename your current  repo  folder at the  kyvosmanagerdata/server  location, such as repo_<current version number>. For example, you can rename it repo_2022.1

8. Locate the version to which you want to roll back (for example, 2021.1), and rename its repo folder (such as repo_2021.1) to repo.

9. Locate the build folder of the Kyvos Manager version to which you want to roll back (for example, 2021.1), and verify the correct value of KM_DATA_DIR  in the set env.sh  file in the  bin  folder.

10. Start the required version of Kyvos Manager using the command:
    ./kyvosmanager_war/kyvosmanager/bin/start-km.sh

Kyvos Manager Rollback to previous releases not supporting Flexible Server

Kyvos Manager rollback to earlier releases (prior to the Kyvos 2023.5 releases that are not supporting Flexible server) when Kyvos Manager using external repository.

• It could be:

  • Kyvos Manager rollback to a release supporting Bundled Postgres: To migrate from external repository to bundled Postgres, see the Configuring jdbc.properties for Kyvos Manager | External Repository to Bundles Postgres section.

  • Kyvos Manager rollback to a release supporting Azure Single Server: To migrate from Flexible Server to Single Server, see the Configuring jdbc.properties for Kyvos Manager | Flexible Server to Single Server section.

Post-rollback steps

If you have rolled back from 2022.1 or above, and you updated the password or encryption algorithm (feature introduced in version 2022.1), then you need to reconfigure the c luster node password on to the previous Kyvos Manager release.