IBM Support

How to Disable the Backup Schedule and Uninstall Velero/OADP in IBM Cloud Pak for AIOps

How To


Summary

This document provides step-by-step instructions for decommissioning the OADP (OpenShift APIs for Data Protection) and Velero backup infrastructure from an IBM Cloud Pak for AIOps (Concert Operate) cluster. It covers two customer scenarios: (1) disabling the backup schedule only, and (2) fully uninstalling the Velero client CLI and the OADP operator.

Objective

  • Disable the automated backup CronJob schedule without removing OADP infrastructure (Option A), or
  • Fully remove the backup Helm chart, OADP custom resources, the OADP operator, and the Velero CLI binary (Option B / full decommission)

Environment

  • Product: IBM Cloud Pak for AIOps / IBM Concert Operate
  • Versions: 4.10.x (steps also applicable to 4.8.x–4.13.x)
  • Prerequisites: oc CLI, helm CLI, velero CLI (for verification only), cluster-admin access

Steps

Before you begin


Set your OADP namespace variable. The default is openshift-adp unless you specified a custom namespace during installation.

export OADP_NAMESPACE=<your-oadp-namespace>   # typically openshift-adp

Part 1: Disable the Backup Schedule (without full uninstall)
The backup schedule is implemented as a Kubernetes CronJob called backup-job deployed via a Helm chart in the OADP namespace.
Option A — Suspend the CronJob temporarily
Use this if you may want to re-enable backup in the future without re-deploying.

# Suspend the CronJob — no future backup runs will trigger
oc patch cronjob backup-job -n ${OADP_NAMESPACE} -p '{"spec":{"suspend":true}}'

# Verify: SUSPEND column should show True
oc get cronjob backup-job -n ${OADP_NAMESPACE}

 

Option B — Uninstall the backup Helm chart
Use this as part of full decommission (required before OADP removal).

helm uninstall backup-job -n ${OADP_NAMESPACE}

Part 2: Fully Uninstall Velero Client and OADP
Step 1: Verify no active jobs are in progress

oc get pods -n ${OADP_NAMESPACE}
velero get backup -n ${OADP_NAMESPACE}
velero get restore -n ${OADP_NAMESPACE}

 

All backup/restore pods should be in Completed state before proceeding.
Step 2: Remove the backup Helm chart (if not done above)

helm uninstall backup-job -n ${OADP_NAMESPACE}

 

Step 3: Delete OADP custom resources

# Remove the primary DataProtectionApplication CR
oc delete dataprotectionapplication --all -n ${OADP_NAMESPACE}

# Remove BackupStorageLocations and VolumeSnapshotLocations
oc delete backupstoragelocation --all -n ${OADP_NAMESPACE}
oc delete volumesnapshotlocation --all -n ${OADP_NAMESPACE} 2>/dev/null || true

# Remove cluster-side Velero backup and restore records
# Note: this does NOT delete data from your S3 bucket
oc delete backups.velero.io --all -n ${OADP_NAMESPACE} 2>/dev/null || true
oc delete restores.velero.io --all -n ${OADP_NAMESPACE} 2>/dev/null || true

 

Step 4: Uninstall the OADP Operator
via OpenShift Console (recommended):

  1. Navigate to Operators → Installed Operators in the openshift-adp namespace
  2. Select OADP Operator
  3. Click Actions → Uninstall Operator
  4. In the confirmation dialog, check Delete all operand instances for this operator
  5. Click Uninstall
    Via CLI:
# List OADP subscription
oc get subscription -n openshift-adp

# Delete the subscription
oc delete subscription redhat-oadp-operator -n openshift-adp

# Delete the ClusterServiceVersion
OADP_CSV=$(oc get csv -n openshift-adp -o name | grep oadp)
oc delete ${OADP_CSV} -n openshift-adp

 

Step 5: Remove the Velero CLI binary from your workstation

rm /usr/local/bin/velero

# Confirm removal
which velero
# Expected: no output or "not found"

 

Step 6: (Optional) Clean up credentials secret

oc delete secret cloud-credentials -n openshift-adp 2>/dev/null || true

Validation

After completing the steps, verify the decommission is complete:

# Confirm backup CronJob is removed
oc get cronjob -n ${OADP_NAMESPACE}
# Expected: No resources found

# Confirm OADP operator pods are gone
oc get pods -n openshift-adp
# Expected: No resources found (or namespace does not exist)

# Confirm no OADP CSV
oc get csv -n openshift-adp
# Expected: No resources found

Notes:

  • The OADP namespace (openshift-adp) can be left in place (empty) if preferred. Deleting the namespace removes all remaining resources at once: oc delete namespace openshift-adp
  • S3 bucket data (backup files) is not affected by any of the above steps. If you also want to remove the backup data, do so separately through your S3/object storage provider.
  • If you later want to re-install OADP for future backup needs, follow the original installation procedure: https://www.ibm.com/docs/en/concert-operate/4.10.1?topic=oadp-installing-backup-restore-tools

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSE9G0Q","label":"IBM Cloud Pak for AIOps"},"ARM Category":[{"code":"a8m3p000000hAHpAAM","label":"Cloud Pak for AIOps-\u003EAI Manager"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.10.0;4.10.1;4.11.0;4.11.1;4.12.0;4.13.0;4.13.1;4.8.0;4.8.1;4.9.0;4.9.1"}]

Document Information

Modified date:
09 August 2026

UID

ibm17283039