Optional: Restoring the Cloud Pak for Data scheduling service

Important: IBM Cloud Pak® for Data Version 4.7 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.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

If the Cloud Pak for Data scheduling service is installed on the cluster, you can restore it.

Before you begin

Before you can restore a backup of the scheduling service on the same cluster, you must uninstall the service. For details, see Uninstalling the scheduling service.

About this task

You do not need to restore the scheduling service to the same cluster if you aren't experiencing any problems with the service.

Permissions needed for this task
You must log in as a user with cluster administrator rights.

For more information about the OADP backup and restore utility, including a list of commands that you can run, see the cpd-cli oadp reference documentation.

Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

Procedure

  1. Restore Kubernetes resource definitions:

    The cluster pulls images from the IBM Entitled Registry
    Restriction: This option is available only if the cluster can connect to the internet.
    cpd-cli oadp restore create ${PROJECT_SCHEDULING_SERVICE}-r1 \
    --from-backup=${PROJECT_SCHEDULING_SERVICE}-b1 \
    --include-resources='namespaces,operatorgroups,configmaps,catalogsources.operators.coreos.com,subscriptions.operators.coreos.com,customresourcedefinitions.apiextensions.k8s.io' \
    --include-cluster-resources=true \
    --skip-hooks \
    --image-prefix=registry.redhat.io/ubi8 \
    --log-level=debug \
    --verbose

    The cluster pulls images from a private container registry
    Restriction: This option is available only if an administrator moved the backup and restore images to the private container registry. For details, see Moving images for the backup and restore utilities to the private container registry.
    cpd-cli oadp restore create ${PROJECT_SCHEDULING_SERVICE}-r1 \
    --from-backup=${PROJECT_SCHEDULING_SERVICE}-b1 \
    --include-resources='namespaces,operatorgroups,configmaps,catalogsources.operators.coreos.com,subscriptions.operators.coreos.com,customresourcedefinitions.apiextensions.k8s.io' \
    --include-cluster-resources=true \
    --skip-hooks \
    --image-prefix=${PRIVATE_REGISTRY_LOCATION}/ubi8 \
    --log-level=debug \
    --verbose

  2. Restore Kubernetes resources:

    The cluster pulls images from the IBM Entitled Registry
    Restriction: This option is available only if the cluster can connect to the internet.
    cpd-cli oadp restore create ${PROJECT_SCHEDULING_SERVICE}-r2 \
    --from-backup=${PROJECT_SCHEDULING_SERVICE}-b1 \
    --include-resources='scheduling.scheduler.spectrumcomputing.ibm.com' \
    --include-cluster-resources=true \
    --skip-hooks \
    --image-prefix=registry.redhat.io/ubi8 \
    --log-level=debug \
    --verbose

    The cluster pulls images from a private container registry
    Restriction: This option is available only if an administrator moved the backup and restore images to the private container registry. For details, see Moving images for the backup and restore utilities to the private container registry.
    cpd-cli oadp restore create ${PROJECT_SCHEDULING_SERVICE}-r2 \
    --from-backup=${PROJECT_SCHEDULING_SERVICE}-b1 \
    --include-resources='scheduling.scheduler.spectrumcomputing.ibm.com' \
    --include-cluster-resources=true \
    --skip-hooks \
    --image-prefix=${PRIVATE_REGISTRY_LOCATION}/ubi8 \
    --log-level=debug \
    --verbose

  3. Validate the Cloud Pak for Data scheduling service subscription.

    The previous step restores the Cloud Pak for Data scheduling service CatalogSource and Subscription. These objects must be validated by comparing the status.installedCSV in the subscriptions.operators.coreos.com custom resource in the Cloud Pak for Data scheduling service project (namespace).

    oc get sub -n ${PROJECT_SCHEDULING_SERVICE} -o jsonpath="{range .items[*]}{.metadata.name}{' - currentCSV: '}{.status.currentCSV}{' - installedCSV: '}{.status.installedCSV}{'\n'}{end}"