Building a backup and recovery plan
Plan backup coverage, recovery priorities, protected copies and restore tests around the systems your business needs to resume work.

A backup job can finish successfully while leaving an important application out of the recovery plan. Files may be recoverable, but the licence, configuration or account needed to use them may be missing.
Start with the work your business needs to resume. Then agree what must be protected, how much recent work you could lose and who will lead recovery. The plan should cover an accidental deletion, failed equipment and an unavailable office as well as a security incident.
Set recovery priorities with the business
List the services people need to deliver work, take payments and communicate. Include cloud applications, shared files and records held only on individual devices. Give each service a business owner and identify its dependencies.
The Cyber Centre’s recovery-planning guidance distinguishes recovery time and recovery point objectives. In practical terms, agree the target time to resume an acceptable service and the amount of recent data loss the business can tolerate.
For example, yesterday’s document copy might be usable while yesterday’s order records leave transactions to reconstruct. Record the decision for each workload. A target is what you design and test against. Check separately what your supplier has committed to.
Match backup coverage to those decisions
Ask IT to show what the current backup includes. Check databases, attachments, permissions, application settings and any required keys. Identify exclusions and who is responsible for protecting each cloud service.
Sync, replication and version history have useful roles, but don’t assume they provide an independently recoverable copy. Deletions or unwanted changes can propagate. Check the recovery scope and limits of each service.
The Cyber Centre’s backup guidance recommends multiple copies across different media, an offsite copy and offline protection. Use it to assess failures that could affect several copies together. A network-connected backup device can also be compromised.
Choose backup frequency and capacity from the agreed recovery needs, data growth and service limits. Set each workload’s schedule separately and check whether the recovery result meets its target.
Protect the copies and recovery access
Restrict backup administration, use supported MFA and protect encryption keys. Check whether someone controlling a normal work account could also delete recovery copies. Make sure a second named person can get into the backups if the usual administrator is unavailable.
If the solution uses retention locks, check which mode is set and who can change it. Our immutable-backup guide covers that configuration separately.
Include privacy, record-keeping and contractual requirements when choosing locations and retention periods. Keep only the information you need, protect it, and confirm how expired copies are removed. There’s no single retention period for every Canadian business.
Write instructions people can follow
Keep a controlled runbook with:
- the order of recovery and who can decide to start it;
- supplier contacts and an alternative communication route;
- the location of recovery instructions, licences and protected keys;
- the environment and dependencies needed for restoration;
- business checks required before staff resume using the system.
Make essential instructions available if work email or the main file store is down. Don’t put passwords or keys into an openly shared checklist.
Test usable recovery and act on failures
Restore representative data into a separate test environment. Check completeness, age, permissions and a real business task with its owner. Record elapsed time, missing dependencies and unresolved gaps.
Assign someone to review failed or missed jobs and storage warnings promptly. Agree restore-test frequency with the owners, then repeat relevant tests after major changes. Our ransomware-readiness exercise tests the wider response handoffs.
During a suspected compromise, involve the response team before reconnecting recovered systems. A successful restore won’t deal with stolen information, and it won’t tell you the environment is safe.
Contact us to review backup coverage and build a recovery plan around the systems your business uses.


