Configuring backups by using the console

Configure the backup and restore function by editing the custom resource (CR) definition for the orchestration instance. You can edit the CR definition from the OpenShift® Container Platform cluster console.

About this task

You can run two types of backup. The backup type that you run depends on which of these types of data you want to back up:
  • Orchestration data, such as assembly and resource packages. This data is stored in a cloud-native PostgreSQL database.
  • Application logging data, such as microservice logs. This data is stored in OpenSearch.

Aside from the wal settings, which apply only to orchestration data backups, the CR settings that you configure in this procedure apply to both types of backup.

Procedure

  1. Log in to your Red Hat OpenShift Container Platform cluster console.
  2. From the navigation menu, click Operators > Installed Operators.
  3. From the list of installed operators, click IBM® Cloud Pak for Network Automation Orchestration Manager.
  4. Click the Orchestration tab.
  5. Click the orchestration instance name.
  6. Click the YAML tab and find the backup section.
    The backup section is in the spec section before the featureconfig section. Search for backup {} if it is the first time that backups are being configured.
    If backups were configured previously, search for bucketName in a backup section.
  7. Enter the information for the backup and restore function. Table 1 in Configuring backups by using the CLI describes the information to enter.
  8. Click Save.

Results

To verify the updates, click the Details tab, scroll to the Backup section in the orchestration overview and review the information.

What to do next

  • Back up the Vault keys for use in disaster recovery by running the following command:
    oc get secret -o yaml cp4na-o-vault-keys -n <cp4na_namespace> > /tmp/cp4na-o-vault-keys.yaml
  • Back up the orchestration CR for use in disaster recovery by running the following command:
    oc get orchestration <instance_name>  -o yaml > /tmp/orchestration-backup.yaml
    
    For example, run a command like this to back up the orchestration CR for the instance name that is called default:
    oc get orchestration default -o yaml > /tmp/orchestration-backup.yaml
    
    Important: If you modify the orchestration CR settings, then you must back up the orchestration CR.
  • Make sure to store the Vault key and the orchestration CR backup in a secure location.