Verify failed (BK-VERIFY)

After a database snapshot is stored, Vigavo checks it: the encrypted file is downloaded, decrypted, decompressed and restored into a separate scratch database, and the row counts of the largest tables are compared with the counts recorded at backup time. A snapshot that passes is marked verified.

BK-VERIFY means this check did not pass. Typical reasons:

• the data changed a lot between the dump and the row count of the manifest (very busy tables);
• an extension or object type in your database that the scratch database cannot load;
• a damaged file (the checksum does not match).

For Supabase Storage snapshots the check compares the manifest with the stored objects and re-downloads a sample of files.

What to do

• Look at the next snapshot: if it verifies, the problem was temporary.
• Prefer a verified snapshot when you restore. Unverified snapshots stay listed, but we do not suggest them first.
• If several snapshots in a row fail to verify, send a ticket with the code and the project name.

A verified snapshot is a good sign, not a guarantee: it shows the file could be restored and the counted rows matched at that time.