THE PRACTICAL CHECKLIST / 12 CHECKS
Backup and Restore Testing Checklist
A completed backup job is useful evidence of a copy being made. A restore test answers a different question: can your business recover information it can actually use? Plan a small, authorized test first, keep it separate from production and record both the result and the remaining gaps.
Your checks stay on this device. No assessment is submitted.
Define the recovery need
Identify essential files, applications and relevant cloud data. Confirm what your backup arrangement includes and what needs a separate solution.
Evidence to look for: A scope list confirmed by service owners.
Source guidance ↗Record how much recent information could be lost and how long the selected service could be unavailable. Use these decisions to guide the backup plan.
Evidence to look for: Business-approved recovery needs in plain language.
Source guidance ↗Check that backup frequency and retained versions support those needs. Identify who receives failure alerts and follows them up.
Evidence to look for: A backup schedule and alert ownership record.
Source guidance ↗Protect the recovery path
Review an offline, offsite or appropriately isolated copy so one failure does not affect every backup. Confirm how that protection works in your chosen service.
Evidence to look for: A documented copy location and separation method.
Source guidance ↗Limit backup access to authorized people. Protect administrator accounts and check whether ordinary production credentials could alter or delete every copy.
Evidence to look for: A backup access review and an owner for gaps.
Source guidance ↗Protect sensitive backup information in transit and storage where supported. Confirm that authorized staff can recover the keys or credentials needed to restore it.
Evidence to look for: A reviewed access and key-recovery process, without secret values.
Source guidance ↗Run a controlled restore test
Select a small sample, an approved operator and a separate destination. Confirm that the exercise will not overwrite live information or interrupt normal services.
Evidence to look for: An approved test scope and destination.
Source guidance ↗Follow the backup provider's supported restore instructions. Record which copy was used, who ran the test and how long the recovery took.
Evidence to look for: A dated test record and actual recovery time.
Source guidance ↗Ask the business owner to open the recovered information and confirm it meets the test's purpose. For applications, include the relevant IT specialist.
Evidence to look for: A usability check and a clear list of missing items.
Source guidance ↗Close the loop
Compare the observed result with the agreed recovery needs. State the exercise's limits instead of treating one successful sample as proof of complete recovery.
Evidence to look for: An outcome summary with scope and limitations.
Source guidance ↗Handle recovered business information under your normal access and retention rules. Agree how temporary test copies will be secured and removed when appropriate.
Evidence to look for: A documented test-copy handling decision.
Source guidance ↗Assign unresolved issues an owner and target date. Repeat the exercise after meaningful changes and at an agreed interval.
Evidence to look for: A follow-up plan and the next test date.
Source guidance ↗TURN THE REVIEW INTO ACTION
Choose the next three moves.
Use the fillable PDF to record an owner and target date for unresolved checks. Keep passwords, recovery codes and confidential system details in your approved internal tools.
Get the action-plan worksheet ↓Sources behind the guidance
Prepared by Canada NexTech. Source guidance checked October 28, 2026.
- Cyber Centre: Baseline controls for small and medium organizations ↗
- Cyber Centre: Foundational security actions (ITSAP.10.300) ↗
- Cyber Centre: Backing up your information (ITSAP.40.002) ↗
This is independent educational material, not an endorsement by the source organizations. Apply the guidance to your own systems with the person responsible for your IT. A completed checklist is not a certification or a complete security assessment.
