Backup / restore drill for Postgres

[aji70]

Description (Contract)

Ops doc.

Tasks

• Implement the change in the relevant code paths
• Wire or persist state where the feature touches runtime behavior
• Add tests (unit, integration, and/or contract/UI as appropriate)

Additional Requirements

• Handle stale, disconnected, or invalid states gracefully where applicable
• Follow existing patterns in this repository (linting, modules, security)

Acceptance Criteria

• Backup / restore drill for Postgres is done and verifiable (CI and/or a short manual checklist)
• No regressions in closely related user or API flows

[kelly-musk]

@kelly-musk has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I would love to work onthis issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kelly-musk to this issue.

[drips-wave]

Congratulations, @kelly-musk! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @kelly-musk: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊