Free tools Windows power users keep installed
One-click scans. No signup required.
Restore the backup to an isolated local Supabase database or a separate project, then verify the schema, representative data, permissions, row-level security (RLS), and the queries your application depends on. A successful restore command proves only that a restore completed; it does not prove the database behaves correctly, or that Storage files and other Supabase services are recoverable.
Choose a safe restore target
For local inspection, Supabase documents restoring a downloaded backup with supabase db start --from-backup. Check the backup’s Postgres version and set the local version to match it. Supabase’s local restore guide says local restore support starts at Postgres 15.1.0.55; backups from older hosted versions may not restore locally. The locally started database is for development, not production use. See Supabase’s local restore instructions.
As an Amazon Associate I earn from qualifying purchases.
A separate hosted project can provide a closer hosted-project environment, but Supabase describes restoring to a new project as a beta, database-only feature. Review the project’s access, billing, settings, and enabled extensions before restoring. Extensions with external operations may start running when the restore completes; inspect scheduled jobs, webhooks, and wrappers to avoid unintended effects. Details are in Supabase’s new-project restore guide.
- Local target: suited to repeatable database inspection; check Postgres-version compatibility and treat the copied data as sensitive.
- Separate hosted project: closer to a hosted restore environment, but project-level components need attention and extension side effects must be considered.
Use controlled credentials and protect copied production data as carefully as the original. Do not test by overwriting the live project: hosted restores can make a project inaccessible during restoration, with downtime depending on database size.
#1 Best Overall
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
Restore and connect
- Identify the recovery point and source version. Record which backup or point in time you selected and the source Postgres version.
- Prepare the isolated destination. For a local restore, match the backup’s Postgres version and follow the documented CLI restore steps. For a hosted restore, use a separate project and review the beta feature’s scope and operational cautions.
- Wait for the restore to finish and capture errors. For PITR, restore duration varies with the time since the last full backup, WAL activity, and database size; Supabase does not give a fixed duration. See its PITR restore-duration guidance.
- Connect to the restored database. Supabase documents connecting to a local restored database with
psql. Use the destination’s connection details, not credentials for production. - Confirm basic query access. Run a harmless query, such as
SELECT current_database(), current_user;. A connection and query show that the database is reachable; they do not establish that expected application data or behavior is present.
Verify schema and data
Compare the restored database with a known schema baseline, source environment, or expected application version. Supabase’s new-project restore documentation lists schema, tables, views, procedures, data, indexes, roles, and permissions among the copied database content. For each item your application relies on, confirm that it exists and can be used.
- Schema: check expected schemas, tables, views, procedures, and indexes.
- Data: query representative records, including records created or changed near the chosen recovery point.
- Relationships and constraints: check important foreign-key relationships and application invariants; compare known row counts where those counts are meaningful.
- Roles and permissions: verify expected roles and grants, then check access using the roles the application actually uses.
Do not treat matching table names or a plausible total row count as sufficient. A targeted query that exercises a critical relationship or application invariant can reveal missing or inconsistent data that a successful restore alone cannot.
Rank #2
- Complete Phone & Computer Backup - Automatically protect photos, documents and videos from iPhone android, Mac and Windows to one secure location
- Your Private File Cloud - Access files from anywhere and share large projects with family or clients without relying on expensive cloud subscriptions
- Smart Home Security Hub - Monitor your home 24/7 with AI-powered surveillance that detects people, vehicles and sends instant alerts
- 100% Data Ownership - Keep full control of your personal data with multi-platform access and no monthly subscription fees
- 2-Year Warranty - Reliable hardware backed by Synology's expert customer support team and ongoing software updates
Test application behavior and RLS
Run the queries and access patterns that matter to the application, using representative roles rather than only an administrative connection. In particular, test row-level security (RLS) policies with both permitted and denied access patterns. Check returned rows and expected errors or empty results; a test run only as an owner or elevated role may not exercise the policy behavior users encounter.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Make the checks repeatable. Supabase documents two approaches in Testing Your Database: write tests using a Supabase client in the application’s language and framework, or write SQL tests and run them through the Supabase CLI. Include checks for critical query results and access rules, and rerun the same suite during later backup drills.
Rank #3
- One Place for All Your Data - Consolidate scattered files from multiple computers, phones and external drives into one accessible hub with 100% ownership
- Professional File Collaboration - Share projects with clients, sync documents across teams and maintain version control without Dropbox fees
- Automated Backup Protection - Set-and-forget backups for Macs, PCs and mobile devices to multiple destinations including cloud and external drives
- DIY Surveillance System - Transform IP cameras into a professional monitoring solution with motion alerts, recording schedules and remote viewing
- 2-Year Warranty - Reliable hardware backed by Synology's expert customer support team and ongoing software updates
Check what a database restore does not recover
A verified database is not automatically a complete Supabase project recovery. Supabase says database backups include Storage metadata but not the underlying Storage API objects. If the application needs uploaded files, separately check that the referenced objects and bucket configuration are available.
A new-project restore also requires manual reconfiguration of project-level components. Supabase identifies Storage objects and settings, Edge Functions, Auth settings and API keys, Realtime settings, extensions and database settings, and read replicas as items that require attention. Check the services your application uses rather than assuming they were restored with the database.
Rank #4
- Team Productivity & Media Hub - Share large files and stream media across your office with 278 MB/s speeds; support concurrent access from 10+ users
- Centralized Repository - Store company documents, client files and media assets with granular access controls and audit logs
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Professional Surveillance System - Monitor home or business with support for 30 IP cameras, motion detection and secure remote access
- 3-Year Warranty & Enterprise Support - Dedicated technical account management is available for business-critical production environments
Daily backups do not store passwords for custom roles. Reset those passwords after restoring if those roles need to authenticate. Supabase describes this limitation in its Database Backups guide.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minutePreserve access to Vault-encrypted data
If the database uses Vault-encrypted secrets or columns, include key handling in the restore plan. Supabase says same-project restores and its new-project restore feature preserve or copy the encryption root key. A manual pg_dump/pg_restore migration to a new project instead creates a project with its own key; copy the old root key if the restored encrypted values must remain readable. Test decryption in a controlled way and do not expose secret values in logs. See Supabase Vault documentation.
Best Value
- Multi-User Video Editing - Support 50+ concurrent users editing 4K/8K projects with 2,239 MB/s speeds; run databases, VMs and media services simultaneously
- Expansive Production Storage - Grow from 160TB to 360TB using expansion units; perfect for growing video archives, post-production workflows and broadcast media
- Flexible High-Speed Networking - Choose 10GbE or 25GbE network upgrade cards to support demanding creative teams and large file transfers
- Enterprise Data Protection - High-availability clustering, automated failover and comprehensive backup to prevent any data loss scenario
- 3-Year Warranty & Enterprise Support - Dedicated technical account management is available for business-critical production environments
Know which backup path you are testing
The restore route and recovery point affect what the drill establishes. Supabase’s current Database Backups guide says projects on Postgres 15.8.1.079 and newer use its newer physical backup process, with physical backups enabled by default for eligible projects. It distinguishes physical backups from logical backups. A physical-backup/PITR setup does not necessarily provide a downloadable logical backup file; Supabase documents the CLI or pg_dump as options for making a logical export in that situation: Downloading logical backups with physical backups enabled.
| Recovery path | What you select | What to verify |
|---|---|---|
| Daily backup | A retained daily backup snapshot. | That the chosen snapshot restores and contains the schema and data expected at that recovery point. |
| Point-in-Time Recovery (PITR) | A restore point within the configured recovery window; Supabase describes restore points with up-to-seconds granularity. | That the chosen point restores and that the resulting data reflects the expected state at that time. Supabase states a worst-case RPO of two minutes on its Database backups feature page; this is a vendor-published claim, not a guarantee for every system or incident. |
| Logical export and restore | A logical dump made with the CLI or pg_dump, where available. |
That the dump can be restored and that its schema, data, roles, and application behavior pass the same checks. A manual migration to a new project has Vault key implications described above. |
For daily backup access, Supabase’s current documentation lists 7 days for Pro, 14 days for Team, and up to 30 days for Enterprise. These are vendor-stated plan windows, so check the live backup documentation before relying on a particular retention period. Supabase says enabling PITR replaces daily backups while PITR is active; confirm the configured recovery window and current plan terms for the project.
Hosted restores can also affect subscriptions and replication slots, which may need to be dropped and recreated. Supabase says the Realtime slot is handled automatically. Account for this when testing a hosted recovery path; a successful database query does not prove that downstream replication or integrations are functioning.
Recommended Free Tools
Make the drill useful
Record the backup or recovery point, source and destination Postgres versions, restore errors, elapsed time, and results of schema, data, permission, RLS, and application-query checks. Record any manual project configuration and file-recovery work separately. Repeat the drill after material schema or backup-process changes. A passing database test establishes only the behaviors you exercised at that restore point, not the availability of every file, service, or integration.
Quick Recap
What to do if the restore or checks fail
- Local restore fails before inspection: check the backup’s Postgres version against the local version and the documented minimum of
15.1.0.55. An older hosted version may not be supported by the local restore route. - Database queries work but application checks fail: compare expected schema and data, then verify grants and RLS behavior under the application’s actual roles.
- Encrypted values are unreadable: determine whether the path created a new project key. For a manual dump/restore migration, confirm that the original Vault root key was copied when needed.
- Database checks pass but the application is still incomplete: verify Storage objects and project-level services separately; those are not all represented by a database restore.
- PITR takes longer than expected: account for elapsed time since the last full backup, WAL activity, and database size rather than assuming a fixed restore time.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
