tegwick 085c1534e0 feat: complete WP-0002 T05 full restore and PITR

First Backup 48s. Full restore 65s (audit_core 30=30). PITR 65s
after retarget (keep present, destroy absent). Scratch namespace
deleted. Production stayed Ready.

2026-08-14 20:24:30 +02:00

1.7 KiB

Raw Blame History

RESOURCE-WP-0002 T05 — production Barman restore evidence

Date: 2026-08-14
Status: verified
JSON: docs/evidence/RESOURCE-WP-0002-T05-restore-2026-08-14.json

What was enabled

platform-pg spec.backup.barmanObjectStore → s3://railiance-platform-pg-backup/platform-pg/
ScheduledBackup platform-pg-daily (immediate: true, 02:15 UTC)
First Backup platform-pg-daily-20260814181421 completed in 48s
ContinuousArchivingSuccess; WAL uploaded with barman-cloud-wal-archive

Full restore

Scratch cluster platform-pg-restore-full in namespace platform-pg-restore (not databases). Ready in 65s.

Check	Production	Scratch
`audit_core.events`	30	30
`events_append_only`	1	1
isolation non-system schemas	2	2

Restore also showed a leftover app database (7.9 MB) that production does not list. Consumer databases matched. Not recovered in place.

PITR

Markers written only in platform_meta.t05_restore_probe on production (keep then destroy), then dropped after evidence.

keep at 18:16:54.128693+00
destroy at 18:17:11.932371+00
First target 18:17:08 failed: PostgreSQL stopped redo at last completed txn 18:16:54 (recovery ended before configured recovery target was reached).
Retarget 18:16:55.128693+00 succeeded in 65s. Scratch table had keep only. audit_core.events still 30.

Cleanup

Scratch namespace platform-pg-restore deleted after this file was written. Production cluster remained Ready. Probe table dropped.

1.7 KiB Raw Blame History Unescape Escape