Important Points

This section provides important considerations and recommendations to follow during Kyvos upgrade and related operations.

• From Kyvos 2026.1 onwards, Kyvos rollback restores the RDS repo state using a PostgreSQL dump taken earlier during the upgrade via pg_dump. This process remains the same for rollback to an older Kyvos state backed up using an RDS snapshot. During the rollback process, the repository database state is restored using either:

  • the database dump, or

  • the RDS snapshot,
    depending on how the Kyvos database backup was originally created for that state.

• From Kyvos 2025.10 onwards, heterogeneous repository types are no longer supported.

• For enforcing free disk space for the required partition, see the Verifying free disk space for partition section.

• For Azure, before upgrading, it is recommended that you remove the previously installed Jar files from Databricks to prevent overwriting or corruption of Jar files.

• For AWS, the restoration process for the external repository RDS has been automated, eliminating the need for manual intervention.

• For AWS, if Kyvos is using an external repository RDS as its repository, before initiating a Kyvos rollback, ensure that the 'UsedBy' tag with a value of 'Kyvos' is added to the RDS subnet/security group used for creating the database instance, if it has not already been added.

• In case of a Rollback, the previous state of Kyvos is restored. In case you made any entity-specific modifications like changes to the semantic model design, registered files, users, etc., Kyvos recommends the designers/Admins create a cab as a backup before rollback and import the cab file to the rolled-back version.

• Process operations cannot be persisted.

• If you roll back to a Kyvos Manager process that supports Derby as its repository, any operations, such as audits, events, or other activities (like users add, import, delete, and update) performed using Kyvos Manager build 2023.1 and onwards will NOT be available when you rollback to a Kyvos Manager release previous to 2023.1.

• The rollback operation will take some time to initiate.

• Kyvos rollback to earlier releases not supporting Flexible server:

  • Post Kyvos rollback, configure the single server in Kyvos through the switch repository of Kyvos Manager. The application automatically handles the single server being configured. It must have the same compatible state of the database with the Kyvos release to which rollback is performed.

  • A change in the user name will be required while configuring a single server in the system as it requires appending the server name to the username.