Back to all scenarios
Scenario #398
Storage
Kubernetes v1.25, Velero restore to DR cluster
Stale Volume Handles After Disaster Recovery Cutover
Stale volume handles caused new PVCs to fail provisioning.
Find this helpful?
What Happened
Restored PVs referenced non-existent volume handles in new cloud region.
Diagnosis Steps
- 1CSI logs: volume handle not found.
- 2kubectl describe pvc: stuck in Pending.
Root Cause
Velero restore didn’t remap volume handles for the DR environment.
Fix/Workaround
• Manually edited PV specs or recreated PVCs from scratch.Lessons Learned
Volume handles are environment-specific.
How to Avoid
- 1Customize Velero restore templates.
- 2Use snapshots or backups that are region-agnostic.