Automated pg_dumpall & WAL-G PITR for Supabase Docker — SupaScale Docker Guide
Supabase Cloud bills +$100/mo for 7-day Point-in-Time Recovery (PITR). SupaScale outlines an encrypted 30-day off-host WAL-G + automated restore verification pipeline.
SupaScale minimum floor: 8 GB RAM • Sweet-spot tier: 16 GB RAM (Public vendor rates retrieved 2026-11-12).
Running high-level zstd compression during pg_dumpall without ionice/nice priority caps starves live PostgreSQL disk IOPS and spikes memory pressure during peak traffic!
SupaScale Deterministic Memory Model Table: Automated pg_dumpall & WAL-G PITR for Supabase Docker
| Supabase Docker Subsystem | Baseline Idle Reserve | 50K MAU Projected Reserve | Memory Role |
|---|---|---|---|
| Managed Supabase 7-Day PITR Add-on | +$100.00/mo | +$200/mo (14-day) | Published Add-on |
| WAL-G Continuous Segment Push | ~40 MB RAM | 60s RPO Window | Async WAL Hook |
| zstd -3 Logical pg_dumpall Stream | Low CPU | ~3.5x–4x Compression | Includes Globals |
| Weekly :5499 Disposable Restore Drill | Automated | Verifies auth.users | Tested Recovery |
SupaScale Continuous WAL-G PITR + Encrypted Nightly Dump Cron
# postgresql.conf continuous 60-second PITR archive hook:
archive_mode = on
archive_command = 'wal-g wal-push %p'
archive_timeout = 60
# /etc/cron.d/supascale-backup (Low-priority encrypted dump to independent vault):
15 03 * * * root ionice -c2 -n7 nice -n15 docker exec supabase-db \
pg_dumpall -U postgres --clean | zstd -3 | \
openssl enc -aes-256-cbc -pbkdf2 -pass file:/root/.backup_key | \
rclone rcat offsite-s3:supascale-vault/nightly-$(date +\%F).sql.zst.enc1. SupaScale DR Principle: Combining Logical pg_dumpall with 60-Second WAL-G PITR
Nightly logical dumps provide clean cross-version portability, yet leave up to 24 hours of data loss if an operator runs an accidental destructive SQL query mid-afternoon. Pairing archive_command = "wal-g wal-push %p" with archive_timeout = 60 streams completed 16 MB WAL segments continuously so you can replay transactions up to the exact minute.
2. Preserving Supabase Cluster Roles & Globals in SupaScale Backup Scripts
Running plain pg_dump on a single database omits cluster-level Supabase roles (anon, authenticated, service_role, supabase_auth_admin). We recommend pg_dumpall (or pg_dumpall --globals-only paired with per-DB custom dumps) alongside physical WAL-G basebackups.
3. Enforcing Provider-Independent 3-2-1 Storage Vaults with SupaScale
Never keep your only backup inside snapshots on the same cloud vendor account as production! Stream AES-256 encrypted archives from your primary Hostinger or Vultr server to an independent InterServer Price-Lock storage node.
SupaScale Matched KVM & VDS Tiers for Automated pg_dumpall & WAL-G PITR for Supabase Docker
InterServer Price-Lock Storage & Ryzen Vault (S3 / MinIO + WAL Backups) — SupaScale
From $6/mo (~153k)
Ideal secondary MinIO S3 target + WAL archive vault or month-to-month Ryzen DB host.
Check InterServer Storage Vault Specs for Automated pg_dumpall & WAL-G PITR for Supabase Docker on SupaScale →Hostinger KVM NVMe VPS (1-Click Docker / Coolify + Supabase) — SupaScale
From $4.99/mo (~127k)
12–24 mo KVM 2 (8GB) or KVM 4 (16GB) locks lowest rate + stacks Extra 20% partner discount.
Compare Hostinger KVM VPS Options for Automated pg_dumpall & WAL-G PITR for Supabase Docker on SupaScale →SupaScale rate citation: Public vendor tariffs retrieved 2026-11-12; promotional and renewal prices change — verify exact checkout pricing before ordering.