dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

chore(docs): Update download backup guide with more clarity and links (#43124)

Browse Source
This commit is contained in:
Timothy Lim authored and GitHub committed 2026-02-24 17:38:27 +08:00
1 parent 1d46515edb
commit d31534f8be
1 file changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/troubleshooting/download-logical-backups.mdx
+2 -2
View File
@@ -6,8 +6,8 @@ github_url = "https://github.com/orgs/supabase/discussions/33045"
database_id = "91ae4c49-bf22-4b8c-b96b-cd11f1c38158"
---
When Point-in-Time Recovery (PITR) or physical backups are enabled, Supabase no longer generates the downloadable logical backup file (backup.gz). This is expected, as the backup pipeline switches entirely to physical backups. You can still download backups via the Supabase CLI command `pgdump`.
When Point-in-Time Recovery (PITR) or physical backups are enabled, Supabase no longer generates the downloadable logical backup file (backup.gz). This is expected, as the backup pipeline switches entirely to physical backups. You can still download backups via the [Supabase CLI `db dump` command](/docs/reference/cli/supabase-db-dump) or using [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html).
For step-by-step instructions, check out our guide: [Backup & Restore](/docs/guides/platform/migrating-within-supabase/backup-restore).
For step-by-step instructions using the Supabase CLI, check out the [Backup database using the CLI](/docs/guides/platform/migrating-within-supabase/backup-restore#backup-database-using-the-cli) guide.
You can also learn more about how backups work in Supabase here: [Database Backups](/docs/guides/platform/backups).