BackupDrill @backupdrill

BackupDrill is on DevHunt today! Back up your Supabase database to a bucket you own, then test the restore in a disposable database. Take a look and share your feedback: devhunt.org/tool/backupdri…

BackupDrill is live on TinyLaunch! Back up your Supabase database to your own bucket, then test the backup with restore drills. I'd love your feedback: tinylaunch.com/launch/23628-b…

@doctor_barns @supabase Do you have any database or Storage backups outside the suspended org? If support grants an export window, request the Storage object bytes alongside the database dump, and keep an untouched copy before testing a restore.

@davidtsolheim @glcst @kiwicopple @supabase What recovery point would make it viable for you—seconds/minutes, or daily snapshots? Scheduled logical backups can help with the latter, but they don't replace PITR. Do you also need recovery for Storage files?

@DSanchezProf @SerotinyBuilds Good catch. I'd test anon separately with only the publishable key and no user session, against a row known to exist. Assert the intended public access explicitly—a broken sign-in or missing fixture shouldn't count as a passing isolation test.

@rahafebx0 Nice to see Storage included. One tweak: ON_ERROR_STOP=0 lets schema restoration continue after errors, including failed CREATE TABLE statements. Compare the restored table list with the expected tables before checking row counts.

@OdesseusAI I'd add a recovery rehearsal before launch: restore the database into a clean target, then recover and checksum a sample uploaded file. The Storage file bytes need their own backup path, alongside the database.

@SerotinyBuilds @DSanchezProf Test in staging with two users from different tenants, using their real JWTs rather than a service-role key. Verify own-tenant access works, cross-tenant reads return no data, and cross-tenant writes fail or affect zero rows. Run these checks after migrations.

@tsukky1122 その後、復元は完了しましたか？ 一時停止したプロジェクトの再開でしょうか、それともバックアップからの復元でしょうか？ まだ止まっている場合は、Supabaseサポートに復元ジョブの状態を確認してもらうとよさそうです。

@simoncrypta @BurnedChris @appfactory Do you test the restore against a clean database automatically, or only when needed? Also curious about your artifact retention window, and whether these snapshots are for dev data or disaster recovery.

Did your Supabase database restore bring the files back? Database backups don't include Storage file bytes. BackupDrill captures files once Storage S3 keys are configured. Test the database restore and check the files separately. backupdrill.com/docs/coverage

@superlede Launch day. Proof, not promises.

BackupDrill is live on Product Hunt today. Supabase backups that prove they restore: DB + Storage files to your own bucket, weekly restore drills in a throwaway sandbox, evidence in your inbox. Would love your honest feedback: producthunt.com/products/backu…

npmjs.com/package/backup… Changelog lives in the commits: github.com/backupdrill/cli

backupdrill 0.1.3: - Storage verification is now a random sample per drill (was: first N files — #101 was never checked) - Restore failures no longer blamed on missing sandbox extensions - Free-plan egress docs match Supabase's fair-use flow npm i -g backupdrill

You bring the bucket. You hold the keys. We prove it restores. 🎥

Super @superlede

4 months ago

Someone on r/Supabase asked where BackupDrill actually puts your backups: "Locally? Can you make a video?" So I made one. Under a minute: - your bucket (S3/R2/B2), your keys - never written to our disks - weekly restore drill: verified, destroyed Proof, not promises.

1 0 0 44 0

backupdrill.com Engine (MIT): github.com/backupdrill/cli

BackupDrill backs up your Supabase project — Postgres database and Storage files together — to your own S3/R2/B2 bucket. Then it proves backups work: scheduled restore drills into a throwaway Postgres, graded and emailed. Free plan: 1 project, no card. MIT engine.