A backup job that reports success has proved that software ran. It has not proved that the data can be restored, that the restored application works, or that the business can find the right copy when a server fails at midnight. Verification is the evidence layer between "we have backups" and "we can recover".
This worksheet is designed to be copied into your operations tracker and used every cycle. Each row has an owner, the evidence to attach, a frequency and a sign-off. Complete it honestly. A conditional result with a dated action is more useful than a green dashboard that nobody trusts.
How to use the worksheet
Start by listing every system and dataset that matters, not every server in the estate. For each one, agree a recovery point objective (how much data loss is tolerable) and a recovery time objective (how long recovery may take). Then assign a backup owner and a separate restore tester. The separation matters: the person who configures the job should not be the only person who confirms it works.
Record the worksheet in a spreadsheet with these columns, or use the sections below as they are:
Item | Criticality | RPO | RTO | Backup owner | Restore tester | Last test | Result | Action | Sign-off
Use four result values: Pass, Conditional, Fail and Not tested. "Conditional" requires an owner and a due date. "Not tested" is never a pass.
Section 1: Scope and ownership
| Check | Owner | Evidence | Frequency | Sign-off |
|---|---|---|---|---|
| Systems and datasets are listed with a business criticality | IT lead | Signed scope register | Annually and on major change | IT lead and business owner |
| RPO and RTO are agreed for each critical system | Business owner | Approved recovery targets | Annually | Operations director |
| A named backup owner and restore tester are recorded | IT manager | Responsibility matrix | On staff change | IT manager |
| Data location, retention and legal constraints are documented | Compliance lead | Data map and retention note | Annually | Compliance lead |
| An offline or immutable copy exists for critical data | Backup owner | Configuration evidence and storage report | Quarterly | IT lead |
| Backup scope matches the systems the business actually uses | System owners | Reconciliation of asset list to backup policy | Quarterly | IT lead |
Section 2: Job health
| Check | Owner | Evidence | Frequency | Sign-off |
|---|---|---|---|---|
| Last successful backup is within the agreed schedule | Backup operator | Job report export | Daily | Backup operator |
| Failures alert a named person, not only a shared inbox | IT lead | Alert rule and test message | Quarterly | IT lead |
| Backup window completes before business hours | Backup operator | Job duration trend | Weekly | IT lead |
| Storage capacity has headroom for the next cycle | Infrastructure owner | Capacity report | Monthly | IT lead |
| Backups are encrypted and keys are available to the recovery team | Security lead | Configuration record and key test | Quarterly | Security lead |
| Credentials and agent versions are current | Backup operator | Version inventory | Monthly | IT lead |
| Job logs are retained long enough to investigate a failure | Backup operator | Log retention setting | Annually | IT lead |
Section 3: Restore testing
| Check | Owner | Evidence | Frequency | Sign-off |
|---|---|---|---|---|
| A single file or record can be restored to a test location | Restore tester | Test record with timestamps | Monthly | Restore tester |
| A database can be restored to an isolated environment | Database owner | Restore log and validation query | Quarterly | Database owner |
| The application starts and passes a smoke test after restore | Application owner | Smoke-test checklist | Quarterly | Application owner |
| Restore time is measured against the agreed RTO | Restore tester | Start and finish times | Quarterly | IT lead |
| Row counts, checksums or document totals match the source | Data owner | Comparison report | Quarterly | Data owner |
| Restored data is deleted or secured after the test | Restore tester | Cleanup record | Quarterly | Security lead |
| Lessons and failures are logged with a due date | IT lead | Action log | Quarterly | IT manager |
Section 4: Integrity, security and access
| Check | Owner | Evidence | Frequency | Sign-off |
|---|---|---|---|---|
| The restore environment is scanned before data is returned to production | Security lead | Scan result | Quarterly | Security lead |
| Access to backup consoles and storage is limited to named roles | Identity owner | Access review export | Quarterly | IT manager |
| Multi-factor authentication protects administrative accounts | Identity owner | Configuration screenshot | Quarterly | Security lead |
| Deleted or expired data cannot be silently restored into production | Security lead | Restore policy and test case | Annually | Compliance lead |
| Backup copies are protected from ransomware deletion or modification | Infrastructure owner | Immutability setting and audit log | Quarterly | IT lead |
| Third-party backup providers are covered by a contract and an access review | Vendor manager | Contract and review note | Annually | Finance director |
Section 5: Retention, legal hold and disposal
| Check | Owner | Evidence | Frequency | Sign-off |
|---|---|---|---|---|
| Retention periods match policy and applicable legal requirements | Compliance lead | Retention schedule | Annually | Compliance lead |
| Expired backups are deleted on schedule | Backup owner | Deletion log | Quarterly | IT lead |
| Legal holds are applied and released with a record | Legal contact | Hold register | On event | Legal contact |
| Archive media and cloud archives are labelled and locatable | Backup owner | Archive inventory | Annually | IT lead |
| Disposal produces a certificate or a verifiable deletion record | IT asset owner | Disposal certificate | On event | Compliance lead |
Section 6: Documentation and escalation
| Check | Owner | Evidence | Frequency | Sign-off |
|---|---|---|---|---|
| The recovery runbook is current and usable by someone who did not write it | IT lead | Runbook review record | Quarterly | IT manager |
| The escalation list includes internal owners and vendor contacts | Service owner | Contact sheet with test date | Quarterly | IT manager |
| Recovery dependencies are documented, including identity, network and licences | Application owner | Dependency map | Annually | IT lead |
| The last test findings are closed or have an accepted risk note | IT lead | Action log | Quarterly | Operations director |
| A one-page result is shared with management | IT manager | Signed summary | Quarterly | Operations director |
Scoring and sign-off
Treat four items as critical: an agreed RPO and RTO, a completed restore test, a protected offline or immutable copy, and available encryption keys. A worksheet with any critical item marked Fail is a fail overall, regardless of the other results. A worksheet with only non-critical gaps is Conditional, provided every gap has an owner and a due date. Only a worksheet where every critical item passes and every action is closed should be recorded as Pass.
Sign-off block: IT lead, business owner for the recovered system, and the manager accountable for operations. Record the date, the systems tested, the result and the next scheduled test. If a test is postponed, record the reason and the new date; do not leave the previous pass in place.
Review cadence
- Daily: job success and alert triage.
- Weekly: capacity, failed jobs and backup window performance.
- Monthly: file-level restore and access exceptions.
- Quarterly: full restore test, security review, documentation check and management summary.
- Annually: scope, retention, contracts and recovery targets.
Backup verification is part of Managed Technology & Cybersecurity, alongside monitoring and recovery planning. The pricing page explains how a verification retainer is scoped. For the budget side of recovery testing, read what backup and disaster recovery testing costs in Bangladesh.
Sources
- NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems, accessed 17 November 2026.
- CISA, Cyber Essentials, accessed 17 November 2026.
- ISO/IEC 27001, Information Security Management Systems, accessed 17 November 2026.
- AWS Well-Architected Framework, Reliability Pillar, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.