Configuring backups by using the CLI
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® CLI.
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
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:
For example, run a command like this to back up the orchestration CR for the instance name that is calledoc get orchestration <instance_name> -o yaml > /tmp/orchestration-backup.yaml
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.