Backup and restore

    You must before shutting down a cluster; etcd is the key-value store for OKD, which persists the state of all resource objects. An etcd backup plays a crucial role in disaster recovery. In OKD, you can also replace an unhealthy etcd member.

    When you want to get your cluster running again, .

    You might run into several situations where OKD does not work as expected, such as:

    • You have a cluster that is not functional after the restart because of unexpected conditions, such as node failure, or network connectivity issues.

    • You have deleted something critical in the cluster by mistake.

    • You have lost the majority of your control plane hosts, leading to etcd quorum loss.

    You can always recover from a disaster situation by restoring your cluster to its previous state using the saved etcd snapshots.

    Additional resources

    Application backup and restore operations

    As a cluster administrator, you can back up and restore applications running on OKD by using the OpenShift API for Data Protection (OADP).

    OADP has the following requirements:

    • You must be logged in as a user with a role.

    • You must have object storage for storing backups, such as one of the following storage types:

      • OpenShift Data Foundation

      • Amazon Web Services

      • Microsoft Azure

      • Google Cloud Platform

      • S3-compatible object storage

    Backing up and restoring applications

    You back up applications by creating a Backup custom resource (CR). You can configure the following backup options:

    You restore applications by creating a CR. You can configure restore hooks to run commands in init containers or in the application container during the restore operation.