verified
NEW IN v3.8.0
Dry-Run Verify
Verification always compares against the fingerprint from backup time — not your live production database.
- During backup (automatic): SHA256 of the file + approximate row count per table from the source DB
- Quick verify: file integrity (hash) only — no database connection
- Deep verify (optional): restore to a temporary database, exact
COUNT(*), compare to fingerprint, then drop the temp DB - Supported on SSH and WordPress hosts
- Production is never replaced; the destination host must allow import
- Older backups without fingerprints need a new backup;
.sql.gzmust be on local disk (S3 sync sends metadata only)
| Result | Meaning |
|---|---|
| SHA256 OK + rows match | File intact; restore matches fingerprint |
| SHA256 OK + rows differ | File intact; row diff not always corruption (InnoDB estimates) |
| No fingerprint | Pre–v3.8.0 backup — take a new backup |