Restore the whole dependency chain
A database snapshot without media or encryption keys may restore only part of the service. Document the application version, schema, storage location and protected key material required to recover the same pod.
Measure recovery under realistic conditions
Restore into a clean environment, check representative articles and media, start workers and test domain routing. Record elapsed time and the latest recoverable transaction. These measurements inform RTO and RPO discussions.
Separate recovery from cloning
A new pod starts with fresh credentials and clean tenants. Recovery of an existing pod preserves the data identity and handles old encryption keys securely. Confusing those two workflows can make intact backups unusable.
