SafeGrd distinguishes an archive check from a real database restore
SafeGrd backs up PostgreSQL and schedules verification in two different forms: replaying the archive without a database server, or restoring into a throwaway PostgreSQL instance. The latter can run custom SQL checks as well as compare counts. Backups are encrypted on the source host and stored in an Object-Locked S3 bucket. The distinction matters because a successful archive replay is not the same test as booting a database.
SafeGrd · PostgreSQL.org · Oct 22, 2026
Why it matters
A recovery claim becomes more useful when it states exactly what was restored and which checks passed.
More context
Try a disposable database on PostgreSQL 13 or later, with a host that can reach it and the required read permissions. The free plan covers one database with weekly in-memory drills; paid plans add sandbox drills. Review key custody and restore location before enrolling.
Keep in mind
This is a proprietary service with BSL-licensed CLI source. Count checks and signed records do not establish application correctness or replace a full recovery exercise.
Original read