Skip to content
Experiencing a breach? Get help now
Cyberphore

Backup and ransomware recovery

Ransomware Can't HoldWhat We Can Restore.

Immutable backups and Microsoft 365 protection, restore-tested every quarter, so ransomware can lock your files but never your business.

Restore tests a year
4
Incident engagement
1 hour
Backup monitoring
24/7
CONSOLE00:00:00 CST3MT

Assets / Backup

Backup health

Sample data

Certified partner of

Why this cannot wait

Encrypted ransomware victims that restored from backups, a 6-year low
54%
Sophos, The State of Ransomware, 2025
Average cost to recover from a ransomware attack, excluding ransom
USD 1.53M
Sophos, The State of Ransomware, 2025
Spent by Canadian businesses recovering from cyber incidents, 2023
CAD 1.2B
Statistics Canada, Canadian Survey of Cyber Security and Cybercrime, 2024

Overview

Most Businesses Have Backups. Fewer Can Prove They Would Recover

Backup and ransomware recovery is the work of keeping copies of your data that an attacker cannot delete or encrypt, and proving you can restore from them within a time your business can survive. We design immutable and offline backups for servers, endpoints and Microsoft 365, test restores on a schedule and write the recovery plan you will follow when a ransom note appears.

Picture a Saskatoon distributor on a Monday morning: file server, accounting system and every connected laptop encrypted. The question is not “do we have backups?” It is “how many days until we can invoice customers again?”

Why So Many Backups Fail During a Ransomware Attack

Because attackers go after them first. Sophos’s State of Ransomware 2025 found that only 54% of organizations whose data was encrypted used backups to restore it, the lowest rate in six years of the survey.

  1. Stage 1

    Get in

    Ransomware crews spend time inside a network before encrypting anything.

  2. Stage 2

    Find the backup console

    It is near the top of their list, often on a server joined to the same domain.

  3. Stage 3

    Destroy the backups

    With the stolen domain admin account, backups are deleted or encrypted.

  4. Stage 4

    Encrypt production

    Only then does the ransom note appear on every screen.

  • Failure point: Backups reachable with the same domain admin credentials as production

    Fix: Separate backup accounts with phishing-resistant MFA, monitored for changes

  • Failure point: No copy offline or immutable, so everything can be deleted remotely

    Fix: At least one copy that cannot be changed or deleted for a set period

  • Failure point: Microsoft 365 not backed up, on the assumption that Microsoft does it

    Fix: Independent backup of Exchange Online, OneDrive, SharePoint and Teams

  • Failure point: Backup jobs failing quietly for weeks with nobody reading the alerts

    Fix: Alerts on failed jobs and deleted restore points, reviewed by analysts

  • Failure point: No one has ever timed a full server restore, so the real RTO is unknown

    Fix: Scheduled, timed restore tests with failures fixed and retested

Ransomware-resistant design

The 3-2-1 Rule Is the Start. Ransomware Needs Two More Conditions

The classic 3-2-1 rule still works as a starting point: three copies of your data, on two different types of storage, with one copy offsite. For ransomware, add two more conditions.

One Copy Is Immutable or Offline

Immutable:
cannot be changed or deleted until a set retention period expires, even by an administrator. The storage platform enforces it, for example object lock on cloud storage or a hardened backup appliance.
Offline:
physically or logically disconnected, with its own credentials.

Either way, an attacker who controls your network cannot reach it.

Backup Access Is Kept Separate

The backup system uses its own accounts, not domain accounts, protected with phishing-resistant MFA and monitored for changes. Our identity and access management service covers separating admin roles properly.

The Canadian Centre for Cyber Security’s ransomware guidance makes the same points: keep backups offline or otherwise isolated, and test that you can restore from them.

RTO and RPO

How Long Each System Can Be Down, and How Much Data It Can Lose

Start with the business, not the technology. Ask what each system does and what an outage costs, then design backups to meet a target you chose deliberately.

Recovery point objective (RPO)
How much data you can afford to lose, measured in time since the last good backup.
Recovery time objective (RTO)
How long a system can be down before the impact becomes unacceptable.

Shorter targets cost more. Your numbers depend on your operations, contracts and how much you are willing to spend. We agree them for each critical system, in business terms, with leadership sign-off.

Accounting and Invoicing

Example targets, not recommendations

RPO: data lost

Up to 4 hours

RTO: time down

Up to 1 business day

Last good backupRansomware hitsRunning again
Why it matters
Cash flow stops without it.
Backups needed
A good restore point at least every 4 hours
Restore must finish
Within 1 business day, proven by a timed test

Restore testing

A Backup You Have Never Restored Is a Hope, Not a Control

Many businesses discover their real recovery time only during an incident, which is the worst time to learn it. Every test is timed, and results go into a short report with what worked and what needs fixing.

What a Test Tells You

  • Whether files are completeSmall restores confirm the data came back intact.
  • Whether the restored server bootsA copy that will not start is not a recovery.
  • How long it really takesThe measured time, not the guessed one, is your real RTO.
  • What you forgotLicence keys, a database password, the order systems need to come back in.

Testing in Layers

  1. Every month

    Small restores

    Files or a mailbox, to prove the backup works and data is complete.

  2. On a set schedule

    Scheduled restore tests

    Timed and documented, with failures fixed and retested.

  3. Once or twice a year

    Full timed recovery

    A critical system restored end to end, to prove you can meet its RTO. Also after major changes such as a server migration.

  4. At least yearly

    Tabletop exercise

    A one-hour walkthrough of the recovery plan with leadership. It finds gaps no technical test will.

The bars show scope, from a single file to the whole business. Restore tests run on a schedule agreed with you.

When the ransom note appears

What a Recovery Looks Like, in the Order It Happens

A recovery plan is the document you pull out when the backups are fine but everything else is not. It should be short enough to use under stress and specific enough that nobody has to guess.

  1. 0

    Investigate Before You Restore

    Restoring before you know how the attacker got in can mean restoring their access too. Our incident response team coordinates investigation and recovery.

    Incident response
  2. 1

    Identity and Core Infrastructure

    Domain controllers and the services everything else depends on. Restoring a file server first usually just wastes hours.

    Clean check before reconnecting

  3. 2

    Systems with the Shortest RTO

    Next come the systems your targets say the business cannot run without, such as accounting and email.

    Clean check before reconnecting

  4. 3

    Everything Else

    The remaining systems, in the order agreed in the plan, until the business is running normally.

    Clean check before reconnecting

Canadian Considerations: Insurance, Privacy and Recovery

Cyber insurance
Canadian insurers commonly ask whether backups are offline or immutable, whether they are tested and how quickly you can recover. Accurate answers matter at claim time.
Insurance readiness
Privacy law
Restoring does not end your obligations. Many ransomware groups steal data before encrypting it. If personal information was taken, PIPEDA may require reporting to the Office of the Privacy Commissioner of Canada and notifying affected individuals; Quebec’s Law 25 and Alberta’s PIPA have their own rules. Backups hold personal information too, so retention and access controls apply to them.
Privacy compliance
Incident response
Recovery should follow investigation, not race ahead of it. Our incident response team coordinates both, and retainer clients get remote engagement within 1 hour.
Ransomware protection overview

General information, not legal advice. Whether to pay a ransom is a decision for you, your legal counsel, your insurer and law enforcement; see the questions below.

Microsoft 365 backup

Microsoft Keeps the Service Running. Protecting Your Data Is on You

Microsoft 365 usually needs its own backup. Its retention features are not designed as protection against an attacker with admin rights or ransomware that syncs encrypted files into OneDrive and SharePoint.

What Microsoft Provides

  • A resilient service that keeps running
  • Retention policies you can configure
  • Recycle bins and version history

Recycle bins have time limits and can be emptied by an attacker with admin rights.

What Remains Your Responsibility

  • Protection from accidental or malicious deletion
  • Protection from an attacker or rogue admin with admin rights, who can empty recycle bins
  • Recovery from ransomware that syncs encrypted files into OneDrive and SharePoint
  • Restore points outside your tenant’s admin reach

A separate backup, from a third party or Microsoft’s own paid backup service, gives you restore points outside that reach.

  • Exchange Online

    Mailboxes, including one that was deleted

  • OneDrive

    User files, including a OneDrive that was encrypted

  • SharePoint

    Sites and document libraries

  • Teams

    Team data and files

Sync is not a backup. OneDrive and Dropbox copy changes, including encrypted or deleted files, to every connected device and the cloud. Treat sync as a convenience for staff and keep a separate backup with its own credentials and retention.

Backup is the last line. Pair it with the prevention controls in our Microsoft 365 and email security service.

How the engagement runs

Assess, Design, Test, Then Keep It Working

  1. 01Assess

    We inventory your systems and data, review current backups and test whether a stolen admin account could destroy them.

    • Backup architecture review: what is backed up, what is not, where copies live, how long they are kept and who can delete them
  2. 02Design

    We set RTO and RPO targets with you, then design backup copies, retention and access controls to meet them.

    • RTO and RPO targets per critical system, with leadership sign-off
    • Design for immutable and offline copies with their own credentials
  3. 03Implement and Test

    Backups are deployed or reconfigured on your existing platform where that makes sense, followed by a full timed restore test of at least one critical system.

    • Immutable and offline copies in place
    • Independent Microsoft 365 backup
    • Recovery plan and runbooks, aligned with your incident response plan
  4. 04Operate

    We monitor backup health, run restore tests on schedule and update the recovery plan as your systems change.

    • Alerts on failed jobs, deleted restore points and backup admin changes, reviewed by analysts
    • Restore test reports

Pricing

Quoted for Your Systems, in CAD

There is no price list. After a free scoping call, you get a written quote in CAD based on what you need to protect and how fast it has to come back.

What moves the price

  • Number of servers, virtual machines and endpoints backed up
  • Microsoft 365 users and workloads covered
  • How short your RTO and RPO targets are
  • Retention periods and immutable storage required
  • Whether we build new or work with your existing platform and IT provider
  • Scope of restore testing and tabletop exercises

FAQ

Backup and Ransomware Recovery: Common Questions

Doesn't Microsoft already back up our Microsoft 365 data?

Microsoft keeps the service running and offers retention policies and recycle bins, but protecting your data from deletion, a malicious admin or ransomware that syncs through OneDrive is your responsibility. Recycle bins have time limits and can be emptied by an attacker with admin rights. A separate backup, from a third party or Microsoft's own paid backup service, gives you restore points outside that reach.

What are RTO and RPO?

Recovery time objective (RTO) is how long a system can be down before the impact becomes unacceptable. Recovery point objective (RPO) is how much data you can afford to lose, measured in time since the last good backup. A four-hour RTO and one-hour RPO for your accounting system drive very different backup choices than three days and 24 hours.

What is an immutable backup?

An immutable backup is a copy that cannot be modified or deleted until a set retention period expires, even by someone with administrator credentials. It is enforced by the storage platform, for example through object lock on cloud storage or a hardened backup appliance. It protects you against the common ransomware tactic of deleting backups before encrypting production systems.

How often should we test restores?

Test something every month and run a larger, timed recovery of a critical system at least once or twice a year, and after major changes such as a server migration. Small file restores prove the backup works. Full system restores prove you can meet your RTO. Many businesses discover their real recovery time only during an incident, which is the worst time to learn it.

Should we pay the ransom if our backups fail?

That is a business decision to make with legal counsel, your insurer and law enforcement. Canadian authorities, including the Cyber Centre, discourage paying. Payment does not guarantee a working decryptor or the deletion of stolen data, and it can make you a repeat target. The best way to avoid the question is backups that attackers could not reach.

Is OneDrive or Dropbox sync a backup?

Not on its own. Sync services copy changes, including encrypted or deleted files, to every connected device and the cloud. Version history and recycle bins help, but they have limits and an attacker with admin access can often remove them. Treat sync as a convenience for staff and keep a separate backup with its own credentials and retention.

Get started

Find Out How Long Your Recovery Would Really Take

A free 30-minute call with a certified specialist. We talk through your systems and current backups, and you get a written quote in CAD.

  1. 1Free scoping callWe map your systems, backups and Microsoft 365, and tell you honestly if a review and a written plan is all you need.
  2. 2AssessmentWe inventory your data, review current backups and test whether a stolen admin account could destroy them.
  3. 3Design, build and first timed restoreTargets agreed, copies deployed or reconfigured, and a critical system restored against the clock.
Ransom note on your screens now? Call 24/7: +1 236 665 1165

Book a Backup and Recovery Review

Free, 30 minutes, no obligation.

Book free assessment