Can your small-business website actually be restored from a backup?
A backup is useful when the business can recover the pages, data, settings, and customer path it needs. Ask what is copied, then test a restore away from the live site.

Your hosting dashboard says “backups enabled.” If the website disappeared this afternoon, could your team bring back the service pages, contact form, images, and recent inquiries? The answer depends on more than whether a copy exists.
Treat a backup as a recovery process you can demonstrate. List what the website needs to work, find out which parts each provider copies, and restore a safe test copy without replacing the live site. A successful test should show both the content and the customer journey working again. If the site handles sensitive records or payments, plan the exercise with the responsible technical and privacy specialists.
This guide is about proving recovery before a problem. Our website security ownership guide covers who maintains the wider set of accounts and protections; our suspected website compromise guide covers what to do when an incident is already underway. In a suspected compromise, preserve evidence and investigate the entry point before restoring a copy.
What the national backup figure can and cannot tell you
Statistics Canada’s 2025 Canadian Survey of Cyber Security and Cybercrime found that 43% of Canadian businesses reported having backups of digital information as a cyber risk management arrangement. The survey covered enterprises with at least ten employees across most sectors, excluding public administration; data were collected in early 2026 about activities in 2025. It does not cover smaller businesses, isolate website backups, or test whether respondents could restore anything. Use it as context for asking a better question about your own site, not as a website recovery rate.
The Canadian Centre for Cyber Security recommends backing up essential business information, keeping it secure, documenting the restore procedure, and regularly checking that recovery works. Those are separate tasks. A green “backup completed” message only addresses the copying step.
List everything a working website depends on
Start with the customer action the site supports. For a simple service website, that may be reading the right page and sending an inquiry to the right person. For a shop, it may include catalogue, orders, and checkout. Then map the parts needed to complete that action:
- Published material: page copy, translations, images, downloadable files, and any content stored in a content management system.
- Working software: the site code or theme, plugins, configuration, and the versions needed to run them safely.
- Changing records: form submissions, booking or order records, and database content, if the site actually stores them.
- Connections: form destinations, email delivery, booking or payment settings, and any credentials or integration settings that must be re-established securely.
- Route to the site: domain, DNS, hosting account, and the person who can change or recover each account.
Do not assume all of these belong in the same backup. A code repository may hold the site files but not a live database. A host’s snapshot may omit email, a separate booking service, or the registrar account. A form provider may hold submissions independently of the site. Ask each provider what they retain and what they can export. Keep an inventory of owners and recovery steps in a secure place the team can reach when the site or normal email is unavailable; keep passwords in an appropriate credential manager rather than in a plain checklist.
For a bilingual site, verify that both language versions, language links, and the inquiry path in each language are part of the recovered result. A restored English homepage alone would leave a large part of the customer experience untested.
Ask the host questions that have testable answers
“Are backups included?” is a start, but it does not define a recovery service. Ask the host or developer to show you:
| Question | What you need to learn |
|---|---|
| What is copied? | The exact files, database, uploads, settings, and services included or excluded. |
| When is each copy made and removed? | Whether the oldest usable copy and the newest possible data loss fit your business needs. |
| Where are copies kept and who can reach them? | Whether a failure or compromised account affecting the live site could also affect every copy. |
| Who initiates and approves a restore? | Which business and provider contacts are available when normal access fails. |
| Where can we test it? | A separate environment that will not replace current content or send test messages to customers. |
| What proof will we keep? | The restored version, missing items, test results, and the owner of each fix. |
The Cyber Centre’s backup guidance recommends copies separate from the original system, protection for sensitive information, and routine recovery tests. Your choices about frequency and retention should follow how much change the business can afford to lose and how quickly the customer path must return. A rarely edited brochure site and a booking system with changing records do not have the same needs. Avoid accepting a universal schedule without checking what actually changes.
Also ask whether a provider’s “restore” means replacing the whole account, one site, a database, or individual files. A broad restore might overwrite legitimate work added after the copy was made. Record who decides what to recover and how recent changes will be reconciled. If a provider cannot answer, document the gap before relying on the service.
Run a safe recovery exercise
Choose a recent known-good copy and a separate test destination. Have the person who would perform a real recovery follow the written steps, with the business owner observing or reviewing the result. The Cyber Centre recommends a test environment so recovery exercises do not interrupt live operations.
Open representative pages and images in the test copy, including mobile and both languages the business offers. Check internal links, any downloadable materials, and a safe test inquiry that goes to a test destination. If the site uses a database, compare a test record that should be present with one created after the selected backup; this makes the possible data-loss window visible. Do not put real customer information into a public test site or trigger live payment, booking, or email workflows by accident.
The technical person should check that the recovered software can run in a supported configuration and that access permissions and integrations are reconnected deliberately. The business owner should check that customers could find the right information and reach the right team. Record what restored, what failed, how long the exercise took, and which missing steps need another test. A partial result is useful evidence for improving the plan; it is not a reason to mark the recovery complete.
This exercise does not prove every future outage will be easy. It proves that a particular copy and procedure worked in a particular test. Repeat it after material changes to the site or provider, and revisit the plan when staff with recovery access leave. The Cyber Centre’s recovery planning guide puts roles, critical systems, recovery objectives, testing, and communication in the same plan.
Decide what is enough for your site
For a simple site whose content is already in a controlled repository, a documented rebuild and a separately protected copy of uploaded content may be more useful than buying another opaque snapshot service. A content management system with frequent edits or a customer database needs closer attention to copy frequency, retention, access, and safe restoration. Compare the work and ongoing cost of each approach with the actual information at risk. A backup product cannot replace a missing domain login or repair an unsafe integration.
Before paying for a new service, ask your current host and developer to demonstrate what they already provide. If the test exposes a gap, decide whether to change the configuration, add a protected copy, improve account access, or move a critical record into a system with a clearer recovery path. Get specialist help where personal information, complex integrations, or a suspected compromise make the test risky.
Red Comet designs and develops business websites. If you are planning a site, bring this inventory to the project conversation so content ownership, provider responsibilities, and a workable handoff are defined alongside the pages and contact route. Confirm any ongoing backup or security arrangement as a separate, explicit responsibility.
Sources
- Statistics Canada, Impact of cybercrime on Canadian businesses, 2025, released October 21, 2026.
- Canadian Centre for Cyber Security, Back up and encrypt data.
- Canadian Centre for Cyber Security, Tips for backing up your information.
- Canadian Centre for Cyber Security, Developing your IT recovery plan.

