Postgres Backup and Operational Readiness

When to use

Invoke when a PostgreSQL deployment needs a verified backup and recovery posture, when validating restore capability against an RPO/RTO before go-live or a reliability review, when defining day-2 operational observability and runbook inputs, or when remediating a backup, retention, or operational-readiness gap.

Do not use for: replication/HA topology and failover (use postgres-replication-and-ha-readiness), schema or migration work (use postgres-schema-and-migration), query/index performance (use postgres-indexing-and-query-optimization), or role/grant/TLS hardening (use postgres-security-and-data-access-hardening).

Inputs

Required:

• The RPO and RTO targets in scope, sourced from reliability-architecture.md where it exists.
• The operational ownership and on-call model, and the alerting/runbook conventions from operations (the operations architecture artifact or the project's operational standards).
• The deployment substrate: self-managed, managed (RDS/Aurora/Cloud SQL), or Kubernetes operator — this constrains the available backup mechanisms.

Optional: