Add Storage Backups in Sync with Database Backups

Currently, Supabase automated backups (and Point-In-Time Recovery) only back up the Postgres database. The Supabase Storage (buckets and objects) are not included in these backups. This creates a serious integrity issue between the database and storage, since restoring a database backup will not restore the corresponding state of files in Storage. Problem • When restoring from a database backup or using PITR, the storage.objects table reflects metadata from a past point in time, but the actual files in the storage bucket reflect the current state. This mismatch can lead to: • Broken links or missing files referenced in the restored database • Orphaned files in buckets that no longer exist in the restored metadata • Data integrity issues for any app relying on synced database–storage relationships • Difficulty in disaster recovery or environment rollback Proposed Solution • Add Storage backups that are automatically: • Included…