☸️

Velero restore failed or incomplete

Backup exists but restore hangs, missing PVCs, or wrong namespace.

Reviewed: ·Tested on: Kubernetes 1.29, Terraform 1.8, Ubuntu 22.04

Symptoms

  • velero restore PartiallyFailed
  • PVC restore stuck
  • Resources missing after restore

1Check restore status and logs

velero restore get
velero restore describe <restore-name>
velero restore logs <restore-name>
Velero guide →

2Common fixes

Storage class mismatch, snapshot provider not installed, or namespace already exists.

# map storage class on restore
velero restore create retry-1 --from-backup <backup> \
  --storage-class-mappings old-sc:new-sc

kubectl get volumesnapshot -A
kubectl get pvc -A
Velero restore snippet →

3Validate restored workloads

kubectl get pods -n <ns>
kubectl rollout status deploy/<name> -n <ns>
Backup hub →

Related

velerokuberneteskubectlk8s-pvck8s-cronjob