Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    PostgreSQL Backup and Restore Drill with PITR Proof

    1

    Prove your Postgres backups restore: audit pg_dump, WAL/PITR, pgBackRest or RDS backups, run a timed restore to a scratch instance, measure real RPO and RTO.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    PostgreSQL Backup and Restore Drill with PITR Proof

    PostgreSQL Backup and Restore Drill with PITR Proof

    Example session with this skill installed

    We run Postgres 16 on a VM with nightly pg_dump to S3 via cron. We think we're fine. Can you check, and tell me how long a restore would take? DB is about 80 GB.

    • Read your context and instructions
    • Compiled the postgresql backup

    Postgres backup drill: prod-db — VERDICT: AT RISK

    Source: PostgreSQL 16.4, 82 GB, self-hosted VM ·

    Targets: not defined (you said "lose at most an hour" → RPO 1 h)

    Backups found

    MethodScheduleLast successLocationEncryptedOff-siteRetention
    pg_dump -Fcnightly 02:0011 days agoS3 same accountSSE-S3no7 days (lifecycle)
    WAL archivingnone—————

    Gaps

    #SeverityGapFix
    1Criticalcron job fails since disk filled (pg_dump: error: could not write); no alertmove dump target off /, alert on missing S3 object
    2Critical7-day retention + 11 days of failures = no usable backup in S3keep 30 days; copy to a second account with object lock
    3HighNo PITR: best case RPO is 24 h vs your 1 hpgBackRest with WAL archiving to S3
    4MediumRoles not backed upadd pg_dumpall --globals-only

    Drill (from a fresh manual dump, to a scratch VM)

    StepDuration
    pg_dump -Fd -j 814:10
    copy to scratch3:40
    pg_restore -j 841:25
    checks (row counts, max(created_at), app queries)4:05

    Measured RTO: 63 min. Restored data matched production at dump time; pg_amcheck clean.

    Next

    Fix 1 and 2 today. Then set up pgBackRest + WAL archiving and re-run this drill as a PITR to a chosen minute. Scratch VM restore-drill-1019 is still running: delete it?

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most teams have backups. Few have restored one. The first real test usually happens during an outage, and that is when people find the dump is empty, WAL archiving failed three weeks ago, roles were never backed up, or the restore takes six hours instead of thirty minutes.

    This skill gives your coding agent a drill procedure and a reference file checked against the PostgreSQL docs. It:

    • Inventories every backup: pg_dump, pg_basebackup, WAL archiving, pgBackRest, Barman, WAL-G, PostgreSQL 17+ incremental backups, and managed backups on RDS, Aurora, Cloud SQL, Azure, Supabase and Neon
    • Finds gaps before you need them: stale or failed backups, WAL archive failures, no encryption, no copy outside the production account, short retention, missing roles/globals, no alerts
    • Runs a timed restore drill to a scratch instance: full restore, point-in-time recovery to a chosen moment, or a single table
    • Checks the restored data: connections, row counts, newest timestamps, extensions, amcheck, app queries
    • Measures real RPO and RTO and compares them with your targets
    • Writes a step-by-step restore runbook from what actually worked
    • Returns a verdict: RESTORABLE, UNTESTED or AT RISK

    Who it is for: founders and small teams running Postgres in production, platform engineers, and anyone answering a SOC 2 or customer security questionnaire about backups.

    Safety: never restores over, drops or reconfigures production. Production access is read-only, restores go to a clearly named scratch target, and restored copies are treated as production data and deleted with your yes.

    Honesty note: RESTORABLE is only given after a restore actually ran and the data checked out.

    Cannot bypass network restrictions or IAM blocks. Requires a scratch instance for drills. Does not handle non-Postgres data like external files or OS-level configs.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 28 days ago

    Requires

    PostgreSQL client tools
    Scratch instance or Docker

    Permissions

    Write Files
    Listed28 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the validation of your PostgreSQL backups by performing non-destructive recovery drills to a scratch environment, ensuring your RTO (Recovery Time Objective) and RPO (Recovery Point Objective) targets are actually achievable before an emergency occurs.

    Any PostgreSQL version your client tools support; the reference file notes features that need newer versions, such as incremental backups in PostgreSQL 17+. It covers self-hosted backups (pg_dump, pg_basebackup, WAL archiving, pgBackRest, Barman, WAL-G) and managed services including AWS RDS and Aurora, Google Cloud SQL, Azure Flexible Server, Supabase and Neon. The restore target should be the same major version as the source.

    Restores always go to a separate scratch instance or container, never to production. Production access is read-only. Note that taking a fresh pg_dump from production for the drill adds read load, so schedule it outside peak hours or restore an existing backup instead.

    A SKILL.md with the drill procedure, gap checklist and verdict rules, plus a reference file comparing backup methods, PITR settings, PostgreSQL 17 incremental backup commands, logical and pgBackRest restore commands, verification queries, and what to check on each managed service. Your agent produces a gap table, timed drill results, measured RPO and RTO, and a restore runbook.

    While the skill automates the logic and command generation, you must provide the agent with network access to your storage buckets and a target environment (like a Docker host or staging instance) where the restore can take place.

    The report records what was restored, when, the commands run, how long each step took, and what was checked, which is the kind of evidence auditors usually ask for when a control requires backup restore testing. Whether it satisfies your specific control is up to your auditor.

    New in Data & Databases