Backup and Recovery for Canadian Businesses
A backup is a copy you can restore. It is not the same thing as a file sitting in a synced folder, and it is not the same thing as a server that has never been tested. The questions that matter are how much work you can afford to redo, how long you can be stopped, and who is allowed to run the restore.
Outsource IT Canada treats backup as part of operating IT for Canadian firms of about 15 to 75 users. Group 4 Networks is 100% Canadian-owned, the team is based in North America, and the office has been in Toronto since 2008. This page explains the decisions. It does not publish a recovery guarantee, because the target has to match your systems.
Recovery point and recovery time
Recovery point is how much recent work you can stand to lose. A nightly copy means up to a day of invoices or notes. A system that takes orders all day may need a tighter point. Recovery time is how long you can be stopped while that copy is brought back. The glossary pages for RPO and RTO define the terms. The numbers belong in your scope, not in a slogan.
Write the numbers per system, not once for the whole company. Email, the accounting file, and a production database do not share one acceptable delay. If the copy holds personal information, the location and who can open it are PIPEDA safeguard questions.
What has to be true for the copy to count
At least one copy should survive the thing you are afraid of. If ransomware can encrypt the laptop and the synced drive, that sync is not the backup. If a fire or a theft takes the only disk in the office, an onsite-only copy is not the backup. Someone should be able to explain the path in one sentence.
Test a restore on a schedule you can put in a calendar. A job that says 'successful' and has never produced a file is a status light, not a plan. The test should name a person, a sample of data, and what 'good' looks like. During tax week, a closing, or a production peak, you want that test already done.
Admin credentials for the backup system are part of the exit plan. If only the provider can see them, you cannot leave cleanly and you cannot restore if the relationship breaks. Documentation is a deliverable.
How backup sits next to support
Monitoring a failed job is daily IT. Redesigning the whole backup platform is a project. The monthly scope should say which one you bought. Standard plans include the help desk on weekdays from 9 AM to 5 PM ET. 24/7 support is available as a paid add-on, which is relevant when a failure happens on a Sunday and the business opens on Monday.
Read the cybersecurity page for how backup fits ransomware, and the cloud page if you are moving systems at the same time. Do not migrate and change backup products in the same weekend unless you enjoy untestable weekends. Call (416) 623-9677 with the system list and the two numbers: how much data you can lose, and how long you can wait.
FAQ
Is Microsoft 365 retention the same as a backup?
No. Retention and a recycle bin help with some mistakes. A backup is a separate copy you can restore when the tenant or the account is the problem. Ask which one you have.
How often should a restore be tested?
Often enough that the last test is still relevant to the systems you run. Put the date in the scope. A test that nobody can remember is not a control.
Do you guarantee a restore time?
No. We agree a target for the systems in scope and we test toward it. A target is not a promise that every failure ends in a fixed number of minutes.