Skip to main content
This page covers the errors the Admin Server returns when it refuses a backup or restore, and how to diagnose a backup or restore that KubeBlocks started but didn’t finish. For how backups work, see Backups & schedules.

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:
For a restore:
The KubeBlocks data protection controller logs the reason for most failures:

A backup is refused

The Admin Server checks a backup or schedule before it creates it.

Volume-snapshot backups are refused

A volume-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 is Pending, read its events:
  • volume node affinity conflict, or no node can be found. The default backup repository is a ReadWriteOnce volume in one zone, and the database is in another. Use an object storage repository or a ReadWriteMany class. 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 datasafed image. Check the pull Secret, or your mirror if you mirror images.
If the pod runs but the backup doesn’t finish, read the pod’s logs for errors writing to the repository, such as rejected credentials or a missing bucket. Check the repository’s settings in Backup Repos in the Admin UI.

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 report Completed, then check the data before you switch clients to it:
If the restore fails, the describe output and the data protection controller’s logs give the reason. Collect a support package for the deployment before you delete anything.