[{"data":1,"prerenderedAt":10},["ShallowReactive",2],{"public:public\u002Fcontent\u002Fdocs\u002Fsupabase":3},{"slug":4,"title":5,"description":6,"draft":7,"updated":8,"html":9},"supabase","Supabase","Keep a pg_dump of your Supabase database in your own bucket and connect it to Verestore with a read-only key.",false,null,"\u003Ch1>Supabase\u003C\u002Fh1>\n\u003Cp>Supabase's daily backups and PITR are restored inside Supabase. To prove your data is recoverable on its own, keep a logical backup in a bucket you control.\u003C\u002Fp>\n\u003Ch2>1. Dump on a schedule\u003C\u002Fh2>\n\u003Cp>Use the \u003Cstrong>session pooler\u003C\u002Fstrong> or direct connection string (Project settings → Database), not the transaction pooler:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-sh\">pg_dump --format=custom --no-owner --schema=public --schema=auth "$SUPABASE_DB_URL" \\\n  | aws s3 cp - "s3:\u002F\u002Facme-backups\u002Forders\u002Fsupabase-$(date -u +%Y-%m-%dT%H-%M).dump"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Run it from a scheduled CI job (see the \u003Ca href=\"\u002Fdocs\u002Fneon\">Neon example\u003C\u002Fa>) or a small server. Include the schemas your application needs; \u003Ccode>storage\u003C\u002Fcode> objects (files) are not in the database and need their own backup.\u003C\u002Fp>\n\u003Cp>Supabase databases rely on roles and extensions that exist on Supabase. The runner creates missing roles as \u003Ccode>NOLOGIN\u003C\u002Fcode> placeholders so the restore completes, and lists them in the report; set the \u003Ccode>extensions_and_version\u003C\u002Fcode> check to \u003Ccode>warn\u003C\u002Fcode> if extensions differ.\u003C\u002Fp>\n\u003Ch2>2. Read-only key for Verestore\u003C\u002Fh2>\n\u003Cp>Create a key limited to listing and reading the prefix: \u003Ca href=\"\u002Fdocs\u002Faws-rds\">AWS S3 policy\u003C\u002Fa>, \u003Ca href=\"\u002Fdocs\u002Fscaleway\">Scaleway\u003C\u002Fa> or \u003Ca href=\"\u002Fdocs\u002Fself-hosted\">S3-compatible\u003C\u002Fa>.\u003C\u002Fp>\n",1794290783591]