How much data could your business afford to lose?
The recovery point objective, or RPO, is the acceptable gap in recovered data. The recovery time objective, or RTO, is the target time to restore operation. These are business requirements, not automatic guarantees from a backup plugin. We use them to plan coverage and a test, then record the observed outcome and dependencies.
Prove backup usability with a restore test
A backup file, a job notification and a tested recovery answer different questions. Identify files, database, uploads, configuration and recovery-access ownership. Agree how secrets are handled without placing them in a public request.
- Agree system and tolerable data gap.
- Inspect coverage, retention and independent access.
- Restore in an isolated environment where feasible.
- Check records and functions, then document gaps.
Backup evidence and recovery limitations
RPO describes an acceptable data gap and RTO a recovery-time objective; neither is automatically a service guarantee. Storage, test environment and production restoration are agreed separately. Do not overwrite recent orders to demonstrate an old copy.
| Check | Evidence | Limit |
|---|---|---|
| Job | Timestamp and asset coverage | Not proof of usability |
| Restore | Data and application checks | May omit external dependencies |
| Access | Owner can retrieve copies | Provider availability remains external |
Example: a restored shop with missing uploads
A shop restores but lacks recent uploads. The report records the missing asset, backup timestamp and resulting data gap before the owner relies on the procedure. This is an illustrative scenario, not a customer case or a promised result.