Backup Verification
A backup is not a backup until you have restored it.
Why verification matters
Most teams discover their backups are corrupted only when they need them. SecureCheap actively verifies your backups so you find out before disaster strikes.
Supported sources
| Source | What we back up | What we verify |
|---|---|---|
| MySQL | Full database dump, gzip-compressed | Gzip integrity, dump structure, table count |
| File / Directory | Tar archive with full path tree | Archive listing, entry count, structure |
| PostgreSQL | Coming soon | — |
| S3 / Object Storage | Coming soon | — |
Verification score (0-100)
Each verification yields a score based on five checks:
| Check | Points |
|---|---|
| File exists on disk | 20 |
| File size is reasonable (> 1KB) | 20 |
| Checksum matches (SHA-256) | 20 |
Gzip integrity test passes (gzip -t) | 20 |
| Dump header contains MySQL signature | 20 |
A score below 80 triggers a critical alert.
How to use it
- Go to Infrastructure → Backup Verify
- Click New Backup Job and configure the source (MySQL credentials, file path, etc.)
- Set a schedule (cron expression — defaults to daily at 3 AM UTC)
- Choose verification frequency (after every backup, weekly, monthly)
- Set retention policy (default: 30 days)
⚠️
Backup verification reads your backup files but never alters production data. The verifier runs in an isolated workspace under /var/backups/securecheap/.
API
POST /api/v1/backup-verify/jobs
POST /api/v1/backup-verify/jobs/:id/run