Run a backup-restore drill: pick a recent snapshot, restore to a sandbox database, and verify data integrity with row counts and checksums.
Executes an end-to-end backup-restore drill: identify a recent snapshot, restore it to a sandbox database, run row-count and checksum integrity checks against a list of critical tables, and produce a drill report.
db_kind: postgres-rds, mysql-rds, or dump-file.source_id: RDS instance identifier or path to a pg_dump / mysqldump file.sandbox_id: a sandbox DB instance to restore into (must be empty or restorable-into).critical_tables: array of fully-qualified table names whose integrity matters most.aws rds describe-db-snapshots --db-instance-identifier <source_id> --query 'DBSnapshots | sort_by(@, &SnapshotCreateTime) | [-1]'. For dump-file, use the path directly.aws rds restore-db-instance-from-db-snapshot --db-instance-identifier <sandbox_id> --db-snapshot-identifier <id>. Dump-file via pg_restore -d <sandbox-conn> or mysql < dump.sql.available: aws rds wait db-instance-available. For dumps, check the restore command exit code.SELECT version(), SELECT current_database().critical_tables: run SELECT count(*) FROM <table> and record. If the source DB is reachable and policy allows, also run the same count on source for comparison.SELECT md5(string_agg(t::text, ',' ORDER BY <pk>)) FROM <table> t LIMIT 100000; MySQL uses CHECKSUM TABLE <table>.<pk> from both source and sandbox; diff via JSON-canonical form.aws rds delete-db-instance --db-instance-identifier <sandbox_id> --skip-final-snapshot.drill-<date>.md containing: snapshot id and creation time, restore duration, per-table row count and checksum match status, sample row diff (if any), and a final verdict (pass if all critical tables match within tolerance). Plus a JSON sidecar for tracking.
The drill is its own verification — pass requires actual restore success and integrity match. As a meta-check, schedule the drill weekly and verify pass-rate stays at 100%; a single fail must trigger investigation. For dumps, also verify file checksum matches the producer's published checksum (sha256sum <dump-file>).
infrastructure-blocker, not a backup failure.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/backup-restore-drill.
Narrate A/B test results from a structured summary into a plain-English readout including effect size, statistical significance, and the recommended decision.
Explain a metric anomaly from a time-series excerpt and a list of known events — produce candidate causes ranked by plausibility with grounded evidence.
Read-only AWS surface — list/describe EC2, S3 buckets, IAM users, and Lambda functions. Auth via STS-assumed role; no mutating tools.
Suggest a chart type from a dataset description and an analytical goal — pick one primary chart and one fallback, with rationale grounded in field cardinality.
Read-only Cloudflare surface — list zones, DNS records, deployed Workers, and page rules. Auth via scoped API token; no mutating tools.
Identify imports and module-init code that contribute to Cloudflare Worker cold starts and propose lazy-load rewrites.