Kubernetes / Storage, Configuration & Data Protection
Design Kubernetes database recovery beyond copying a mounted volume
A live file copy can capture an inconsistent database state even when the PVC is healthy. Inventory the workload and storage before choosing a backup method.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app get statefulset database -o wide
kubectl -n app get pvcRead the result
The inventory identifies workload and claims, not a backup or an application-consistent recovery chain. External databases and encryption keys need separate coverage.
Resolve and verify
Use the database vendor's supported backup workflow, retain manifests and required secrets through secure procedures, and rehearse recovery in an isolated environment.
Before changing production
Do not copy active database files blindly or overwrite the only live claim during a recovery drill.