Backup and restoration for Kyvos external 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)

Note

In AWS, the PostgreSQL dump functionality is currently not working as expected, preventing repository migration due to a version mismatch. Consequently, the switch repository functionality is not supported.

The backup process of the Kyvos external repository for AWS (RDS), Azure (Postgres), and GCP (CloudSQL) has been automated during the upgrade. Similarly, the Kyvos external repository for AWS (RDS), Azure (Postgres), and GCP (CloudSQL) restoration process have been automated during the rollback.

If the automated backup during the upgrade or restoration process fails during rollback, you must resume the steps from the point where it stopped previously. To do this, follow the manual steps mentioned in the below sections.

Manually creating Kyvos external repository for AWS

Manually creating Kyvos external repository for Azure

Note

This applies to Kyvos Enterprise (for external repository based deployment)

Manually creating Kyvos external repository for GCP

Upgrade and Rollback Kyvos from a Previous Version to the Latest for CloudSQL

If you want to upgrade or rollback from any version previous to the current release and to use external repository (Cloud SQL), perform the following steps:

Upgrade the cluster from the previous release to the current version.
Create Kyvos and Kyvos Manager external repository manually.
Switch Kyvos repository from bundle to external.
Switch from Kyvos Manager repository from bundle to external.
Rollback only Kyvos from the current release to the previous version.
Switch Kyvos repository from external to bundle.
Rollback Kyvos Manager.
Switch Kyvos Manager repository from external to bundle.