Creating online backups of Cloud Pak for Data with NetApp Astra Control Center

Important: IBM Cloud Pak® for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

Create online backups of a Cloud Pak for Data deployment with NetApp Astra Control Center.

Before you begin

Ensure that all prerequisite tasks are completed.

About this task

To create online backups, your Cloud Pak for Data deployment must meet the following requirements:
  • The minimum deployment profile of IBM Cloud Pak foundational services is Small.

    For more information about sizing IBM Cloud Pak foundational services, see Hardware requirements and recommendations for foundational services.

  • All services are installed at the same Cloud Pak for Data release.

    You cannot back up and restore a deployment that is running service versions from different Cloud Pak for Data releases.

  • The Cloud Pak for Data control plane is installed in a single project (namespace).
  • The Cloud Pak for Data instance is installed in zero or more tethered projects.
  • Cloud Pak for Data operators and the Cloud Pak for Data instance are in a good state. For more information, see Best practices for monitoring Cloud Pak for Data.

You must be a cluster administrator or a similar role to create backups.

Procedure

  1. In NetApp Astra Control Center, select Applications.
  2. Select the ${PROJECT_CPD_INST_OPERATORS}-tenant application.
  3. From the Options menu in the Actions column for the application, select Back up.
  4. Specify a name for the backup.
  5. Choose a destination bucket for the backup.
  6. Click Next.
  7. Select Back up.

Results

NetApp Astra Control Center does the following actions:

  1. Invokes the pre-backup execution hook.
  2. Captures the ${PROJECT_CPD_INST_OPERATORS}-tenant application Persistent Volumes, PVCs, and cpdbr resources.
  3. Invokes post-backup execution hook.

    ${PROJECT_CPD_INST_OPERATORS}-tenant application resources are captured via OADP.

What to do next

Check that both the State and Hook state columns for the backup show Healthy. If one of the columns shows Unhealthy, the backup is not valid and it cannot be restored.
Tip: A failed execution hook will cause the Hook state column to show Unhealthy.