Backup Verification and Checksums
It is not enough for a backup to exist — it must be intact. Files can become corrupted in storage or transit without any obvious sign. Verification, often using checksums, confirms that a backup is exactly what it should be.
This article explains how we make sure your backups are not just present but genuinely usable.
What a Checksum Does
A checksum is a short fingerprint calculated from a file's contents. If even one byte changes, the fingerprint changes, revealing the corruption.
- Confirms a backup arrived in storage intact.
- Detects silent corruption over time.
- Proves the restored file matches the original.
Verification in Practice
We record a checksum when a backup is created and check it again later. A mismatch triggers an alert and a fresh backup, long before you would ever need to restore.
| Check | What it catches |
|---|---|
| Backup completed | Job failures |
| Checksum match | Corruption or tampering |
| Test restore | Unusable backups |
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.