Switching Kyvos Repository

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

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

The section provides information on the following:

Important points

You can see the last operation details, including progress status and start time, by clicking the i icon. To view more comprehensive details, simply click the View Details link, which will take you to the Operations page, where you can view the operation information in detail.
To avoid semantic model data loss, ensure that before switching ensure property “OBSOLETE_CUBE_PURGE_FREQUENCY“ is set in biserver.properties by increasing the value for it to desired frequency value in which verification that switching worked well can be complete.
If the target repository password is different then only for connection testing purposes password can be specified in provided optional input. If not specified explicitly, Kyvos Manager will use the existing password configured in the system for validating the connection. This is not applicable to GCP.
Before switching the repository ensure that you have data ready in the target Postgres instance to which you are switching.
Dump import and export can be done using pgdump and psql. However, in case of external to external repository change service on the snapshot offered by the cloud can be used to take snapshot from source Postgres and restore it in destination Postgres.
Username and Password and database name in target Postgres instance to which switching to is expected to be same as that of current in-use Postgres instance.
Rollback Scenario: If after an upgrade, the repository is switched then before performing rolling back, ensure it is switched back to the original repository.
Permissions required in role attached on Kyvos Manager node remains same as that of required for automated deployed in case of external repository thus for switching from external repository to external repository no additional permission is required in the role added on Kyvos Manager node.
For switching from bundled to an external repository, you need to add permission on the role attached to the Kyvos Manager node so that fetch or external repository details work. If permission is not added to the role, then the Fetch Details will not work. However, you can still proceed ahead by providing those details manually on provided UI inputs.
If switching to an external repository, then proper network access should be configured.
The security group must have a role granting access to the port used by external repo from BI Server and Kyvos Manager node if it is in the same region and resource group (For Azure Postgres) as that of the cluster.
Following tags are expected on the external repository:
- UsedBy - Kyvos
- ROLE - DATABASE
- LAYER - Metadata_Storage

Using commands to import and export database

Note:

Database name is fixed and always required as delverepo.

For import and export, run the below commands from kyvos/Postgres/bin folder of Kyvos Manager machine.

Connect to Database from terminal

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:{KYVOS_HOME}/Postgres/lib:{KYVOS_HOME}/Postgres/librhel8
./psql -h <HOST-NAME> -p <PORT> -U <USER-NAME>

Database dump Import

Before importing, if database is not created automatically, you must manually create database first using create database command

Execute one of the following commands:

./psql -U <USER-NAME> -p <PORT> -h <HOST-NAME> -d <DATABASE-NAME> -f <FILE-NAME>
./psql -U <USER-NAME> -p <PORT> -h <HOST-NAME> -d <DATABASE-NAME> < <PATH-TO-FILE-IN-WHICH-CONTAINS-EXPORTED-DUMP>

The following tables describes the sample commands. This is ONLY for reference.

Repository	Sample command (for Kyvos database ONLY)

Repository	Sample command (for Kyvos database ONLY)
Import to bundled	./psql -U postgres -p 45421 -h localhost -d delverepo -f db-dump.sql
Import to external	AWS: ./psql -U postgres -p <> -h <> -d delverepo -f db-dump.sql Azure: ./psql -U postgres -p 5432 -h kyvos-postgresserver-1010.postgres.database.azure.com -d delverepo -f db-dump.sql GCP: ./psql -U postgres -p 5432 -h 10.243.140.5 -d delverepo -f db-dump.sql

Database dump export

./pg_dump -c -C --host=<host> --port=<port> --dbname=<database name> --user=<user name> --password=<password> <file name>

The following tables describes the sample commands. This is ONLY for reference.

Repository	Sample command (for Kyvos database ONLY)

Repository

Sample command (for Kyvos database ONLY)

Export from bundled

./pg_dump -c -C --host=localhost --port=45421 --dbname=delverepo --user=postgres --password=<password> dbdump.sql

Export from external

AWS:
./pg_dump -c -C --host=<RDS endpoint> --port=45421 --dbname=delverepo --user=postgres --password=<password> dbdump.sql

Azure:
./pg_dump -c -C --host=kyvos-postgresserver-1010.postgres.database.azure.com --port=5432 --dbname=delverepo --user=postgres --password=<password> dbdump.sql

GCP:
./pg_dump -c -C "host=10.123.230.22 port=5432 dbname=delverepo user=postgres password=<passwd>" > dbdump.sql

Switching repository

Note

Currently, in AWS, the switch repository is not working as expected; therefore, migrating a repository is not supported.

From Kyvos 2025.6 onwards, external Postgres repository version 16 is supported in Azure (Flexible Server) and GCP (Cloud SQL) clouds. To switch between Kyvos PostgreSQL repositories, see the Migrating Kyvos PostgreSQL Repository section.

In the Kyvos 2025.2 release, following switching repository cases not supported:

Switching from an external repository to bundled repository
Switching from external repository to another external repository