Backup failed (BK-* codes)

A backup run connects to your database with the saved read-only user, streams a dump, compresses and encrypts it, and uploads it. If any step fails, the run is marked failed, the error code appears on the Backups tab, and you get a backup_failed alert (critical after three failures in a row). A failed run does not touch your earlier snapshots.

What each code means

• BK-AUTH: the database refused the backup user. The password may have changed; save the connection again.
• BK-NET: the database could not be reached during the backup (paused project, firewall, wrong host). See Connection test failed.
• BK-VERSION: the database server is newer than the dump tool we have for it. Vigavo picks the matching pg_dump per server version; PostgreSQL 17 needs a server update on our side. The message says which versions are supported.
• BK-PERM: the backup user cannot read some tables (permission denied). Run the GRANT lines from the wizard again; new schemas need their own GRANT.
• BK-DUMP: pg_dump or mysqldump stopped with an error. The last lines of its output (with any password removed) are shown under the error.
• BK-DISK: there was not enough temporary space on our side for a large object. Nothing is needed from you; the next run retries.
• BK-SST: the Supabase Storage part failed (for example the Storage key was revoked). The database snapshot of the same run is unaffected. Save a new key on the Backups tab.
• BK-UNKNOWN: anything else. Send a ticket with the code.

Storage and destination

Two more codes have their own articles: BK-CAP (storage full) in Storage caps and retention and BK-DEST (destination missing) in Bring your own bucket.

Next step

After fixing the cause, press "Back up now" on the Backups tab. If you think data is already lost, follow What to do first.