7 Fault Recovery

This chapter provides information about fault recovery for Oracle Communications Cloud Native Core, Certificate Management deployment.

7.1 Impacted Areas

The following table shares information about the impacted areas during OCCM fault recovery:

Table 7-1 Fault Recovery Impacted Areas

Scenario Details Requires Fault Recovery or reinatallation of CNE Requires Fault Recovery or reinatallation of OCCM Comments
1 Complete site failure (due to infrastructure failure e.g. hardware/CNE etc) Yes Yes NA
2 Corruption in OCCM deployment No Yes Only helm uninstallation and installation is done.

7.2 Prerequisites

Before performing any fault recovery procedure, ensure that the following prerequisites are met:
  • Docker images used during the last installation or upgrade must be retained in the external data source.
  • Custom values file used at the time of OCCM deployment is retained. If the custom_values.yaml file is not retained, then regenerate it manually. This task increases the overall Fault Recovery time.

7.3 Fault Recovery Scenarios

This section describes the fault recovery procedures for various scenarios.

7.3.1 Scenario 1: Full Site Failure

Single, Multiple, or all Site Failure

This scenario applies when one, more that one, or all sites have failed and there is a requirement to perform fault recovery.

To recover the failed sites:
  1. Run the Fault Recovery procedure to install Kubernetes cluster
  2. Install OCCM helm charts. For more information about installing OCCM, see the Installing OCCM chapter in the Oracle Communications Cloud Native Core, Certificate Management Installation, Upgrade, and Fault Recovery Guide.

7.3.2 Scenario 2: Corruption in OCCM Deployment

This section describes how to recover when the OCCM deployment is corrupted.

Scenario 2a: OCCM deployment is corrupted

To recover the corrupted deployment:
  1. Run the following commands to uninstall the corrupted OCCM deployment if needed:
    helm uninstall <deployment name> --namespace <deployment namespace>
    For example:
    helm uninstall occm --namespace occm
  2. Use the backed up copy of the custom-values.yaml file to install the OCCM. For more information about installing OCCM, see the Installing OCCM chapter in the Oracle Communications Cloud Native Core, Certificate Management Installation, Upgrade, and Fault Recovery Guide.

Scenario 2b: OCCM configuration data is corrupted

To recover the configuration data:
  1. Run the following commands to uninstall the corrupted OCCM deployment if needed:
    helm uninstall <deployment name> --namespace <deployment namespace>
    For example:
    helm uninstall occm --namespace occm
  2. Run the following command to restore OCCM configuration using the backup copy of occm-config-map:
    kubectl apply occm-config-map_<version>_backup.json

    For more information, see OCCM Configuration Backup.

  3. Use the backed up copy of the custom-values.yaml file to install the OCCM. For more information about installing OCCM, see the Installing OCCM chapter in the Oracle Communications Cloud Native Core, Certificate Management Installation, Upgrade, and Fault Recovery Guide.