Content Comparison

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

...

• 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 olapengine.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.

• For Azure, the Postgres port is fixed (5432) and cannot be specified manually.

• Permissions required in role 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 Database

...

import/export commands

Anchor
commands commands

Anchor
export-importcommands export-importcommands

...

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 the database dump itself doesn't take care of creating database then ensure you have manually create database first using create database command

...

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

...

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.

Switching repository

The section provides information on the following:

...

Switching from bundled repository to external repository

Switching repository

The section provides information on the following:

• Switching from bundled repository to external repository

• Switching from external repository to another external repository

• Switching from an external repository to bundled repository

• Switching to a new bundled repository (recovered state) from the bundled repository (for Disaster Recovery)

Switching from an external repository to bundled repository

Anchor
exttobundled exttobundled

1. Export data from external Postgres (AWS RDS or , Azure Postgres or GCP CloudSQL).

2. In an existing cluster, identify the target node for running bundled Postgres and start the Postgres service on that target node.

3. On the navigation bar, click Utilities > Manage Kyvos Repository.

4. On the Manage Kyvos Repository page, select the Bundled Postgres Repository option (by default, Bundled Postgres will be shown selected).
   

   

5. Select that cluster node from the dropdown on which the data dump is imported in step #2 above.

6. If needed, select the Restore Database Dump option to restore a dump of the Postgres database.

   1. Locate Dump data from:

      1. Restore data from last backup:Select this option to get the data restored from the last created backup.

      2. Upload data dump file: Select this option to upload a previously saved data dump file.

7. Perform repository connection validation using Test Connection link.
   NOTE: In case of any problem with the test connection, you will see an error message. Fix those problems before proceeding with switching the repository.

8. Once the connection is validated successfully, click the Save button. This will configure new Postgres as a repository for Kyvos.

9. Restart the BI Server service.

...

...

6. Perform repository connection validation using Test Connection link.
   NOTE: In case of any problem with the test connection, you will see an error message. Fix those problems before proceeding with switching the repository.

7. Once the connection is validated successfully, click the Save button. This will configure a new Postgres as a repository for Kyvos.

8. Restart the BI Server service.

...