Backup vs PITR
Full backups; point in time.
Overview
Backup vs PITR chooses between full snapshot backups and point-in-time recovery. Full backups are simple but lose everything since the last snapshot; PITR replays WAL for per-second recovery at higher storage cost. The discipline matches RPO to mechanism per database.
- Full backups plus point in time. Per-database recovery option; the choice depends on the RPO requirement.
- Full backups: simple. Per-snapshot full state; matches simple recovery where data loss between snapshots is acceptable.
- PITR: granular. Per-database per-second recovery; matches strict RPO where minutes of data loss is unacceptable.
- PITR cost plus per-database choice. WAL retention adds storage cost; the choice gets made per database based on stakes.
The approach
The practical approach: RPO-driven choice, PITR for strict RPO, full backups for relaxed, per-database decision documented. The team’s discipline produces matched recovery rather than uniform over-investment or under-investment.
- RPO-driven. Per-database RPO target; the recovery mechanism follows the target.
- PITR for strict RPO. Per-strict-RPO database the PITR; the WAL cost is justified by the recovery requirement.
- Full backups for relaxed. Per-relaxed-RPO database the full backup; cost stays low because the requirement is loose.
- Per-database choice plus documented rationale. Per-database recovery target; per-database rationale committed for operational reviews.
Why this compounds
Recovery discipline compounds across databases. Each correct choice produces ongoing recovery confidence; the team’s recovery expertise grows; new databases inherit the per-database decision framework.
- Better recovery. Right mechanism matches RPO; the recovery option meets the actual requirement.
- Better cost efficiency. Right mechanism matches stakes; the team does not over-pay for PITR on workloads that do not need it.
- Better operational fit. Right recovery for the workload; the operations match what the workload demands.
- Institutional knowledge. Each choice teaches recovery patterns; the team’s recovery muscle grows.
Recovery discipline is an operational discipline that pays off across years. Nova AI Ops integrates with backup telemetry, surfaces patterns, and supports the team’s recovery discipline.