Inspect a backup or restore
The Admin UI shows each backup’s status on the deployment’s Backups tab. For the details, look at the KubeBlocks resources and the pods that do the work:A backup is refused
The Admin Server checks a backup or schedule before it creates it.Volume-snapshot backups are refused
Avolume-snapshot backup needs CSI-backed volumes and a VolumeSnapshotClass for their driver. The Admin Server checks this and names what is missing:
Check the classes and drivers in the cluster:
A backup stays Pending or Running
If the backup pod isPending, read its events:
volume node affinity conflict, or no node can be found. The default backup repository is aReadWriteOncevolume in one zone, and the database is in another. Use an object storage repository or aReadWriteManyclass. See Multi-zone clusters.- Insufficient CPU or memory. The node that holds the database volume has no room for the backup pod. Free capacity on that node.
- Image pull errors. Backups run the
datasafedimage. Check the pull Secret, or your mirror if you mirror images.
A restore is refused
A license in
expired or invalid state also refuses restores, because a restore creates a deployment. See Troubleshoot licensing.
A restored deployment has no data yet
A sharded deployment loads its backup once the shards form, so it can show as running before every shard has its data. Wait for the restore to reportCompleted, then check the data before you switch clients to it:
describe output and the data protection controller’s logs give the reason. Collect a support package for the deployment before you delete anything.