Backup And Restore Troubleshooting
Backup and restore failures usually come from cluster credentials, object storage, Velero, or target environment compatibility.
Quick Map
| Symptom | Check First |
|---|---|
| Backup creation fails | Cluster RBAC, Velero namespace, operator logs |
| BSL unavailable | Endpoint, bucket, credentials, CA, network |
| Backup is slow | PVC size, storage throughput, network, Velero concurrency |
| Restored pod Pending | PVC binding, StorageClass, node resources |
| ImagePullBackOff | Registry, imagePullSecret, image rewrite |
| Ingress has no address | IngressClass and target controller |
Commands
kubectl get appbackup,apprestore -A
kubectl get events -A --sort-by=.lastTimestamp | tail -100
kubectl -n disaster-system logs deploy/disaster-operator --tail=300
kubectl -n disaster-system logs deploy/disaster-server --tail=300
Velero checks:
kubectl --context prod-a -n velero get backup,restore,backupstoragelocation
kubectl --context prod-a -n velero logs deploy/velero --tail=300
Fix the root cause before using retry.