Troubleshooting
Problem
- A management backup might remain in a
Pending
state for a long period, particularly after upgrading the management subsystem. A pending backup blocks other backup from completing.
Resolving The Problem
- Verify the names of the pending backup and operation lock by running the following commands:
kubectl -n get mgmtb | grep Pending
kubectl -n get cm | grep oplock
- Delete the pending backup by running the following command:
kubectl -n <namespace> delete mgmtb <name-of-backup>
- Delete the operation lock by running the following command:
kubectl -n <namespace> delete cm <name-of-lock>
To resolve this problem, you must remove the pending backup and operation lock, and then rerun the backup CR. To remove the pending backup and operation lock, complete the following steps:
- Verify the names of the pending backup and operation lock by running the following commands:
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000CeBqAAK","label":"API Connect-\u003EManagement and Monitoring (MM)-\u003EBackup\/restore"}],"ARM Case Number":"TS009757781","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0;10.0.1"}]
Was this topic helpful?
Document Information
Modified date:
01 August 2022
UID
ibm16609066