A.2 Restoring SEPP and cnDBTier

Perform this procedure to restore SEPP, cnDBTier, and SEPP database (DB).

Prerequisites:

• Take a backup of the custom_values.yaml file that was used for installing SEPP.
• Take a backup of the SEPP database and restore the database as described in SEPP Database Backup and Restore. Perform this task once every evening.

If SEPP deployment is corrupted, do the following:

1. Run the following command to uninstall the corrupted SEPP deployment:

   helm uninstall <release_name> --namespace <namespace>

   Where,

   • <release_name> is a name used to track this installation instance.
   • <namespace> is the release number.

   Example:

   helm uninstall ocSEPP --namespace SEPPsvc

2. Install SEPP using the backed up copy of the custom_values.yaml file.

   For information about installing SEPP using Helm, see Installing SEPP section.

If cnDBTier and NF deployment is corrupted, do the following:

1. Install cnDBTier as described in Oracle Communication Cloud Native Core DBTier Installation, Upgrade, and Fault Recovery Guide.
2. Restore SEPP DB as described in SEPP Database Backup and Restore.
3. Install SEPP using the backed up copy of the custom_values.yaml file.

   For information about installing SEPP using Helm, see Installing SEPP section.

If DB Secret or cnDBTier mysql FQDN or IP or PORT is changed, do the following:

1. In the backed up copy of the custom_values.yaml file, update these values: dbHost/dbPort/dbAppUserSecretName/dbPrivilegedUserSecretName.

   # DB Connection Service IP Or Hostname with secret name.
     database:
       dbHost: "mysql-connectivity-service.seppsvc"
       dbPort: "3306"
       # K8s Secret containing Database/user/password for all services of SEPP interacting with DB.
       dbAppUserSecretName: "seppuser-secret"
       # K8s Secret containing Database/user/password for DB Hooks for creating tables
       dbPrivilegedUserSecretName: "seppprivilegeduser-secret"

2. Run the following Helm upgrade command to update the secrets for SEPP control plane microservices, such as configuration, subscription, audit, and notification, to connect to the DB with changed DB Secret or DB FQDN, IP, or Port:

   helm upgrade <release name> -f <custom_values.yaml> --namespace <namespace> <helm-repo>/chart_name --version <helm_version>

   Example:

   helm upgrade ocsepp -f /home/cloud-user/1.12/values.yaml /home/cloud-user/1.11.0/ocsepp --namespace seppsvc