Skip to content
Data protection and recovery

Plan for recovery before you need it.

A useful data protection plan starts with the systems you must recover, the data loss you can tolerate and the time available to restore service. Discuss backup scope, retention, recovery testing and ongoing responsibilities with Robson.
Talk to our team
The two numbers a recovery plan is built on
  1. Last good copy

  2. Recovery point (RPO)How much recent data you can afford to lose.

  3. Incident

  4. Recovery time (RTO)How long you can be without the service.

  5. Service restored

We agree these objectives for each system in scope. They differ by workload, so we do not publish a single recovery guarantee.

Who it serves

Teams responsible for systems that cannot be lost: anyone whose backups have never been fully restored, who is reviewing an existing arrangement, or who must show auditors or a procurement panel that recovery works.

What is included

Backup scope, frequency, retention and restore procedures, defined for each system in your deployment. Backup storage locations are in Canada and documented for your deployment.

Recovery objectives

Recovery point (RPO) and recovery time (RTO) objectives are agreed system by system, because a payroll database and a public website rarely need the same answer.

Recovery testing

A backup is only proven once it has been restored. Restore tests are scheduled, run and recorded, so you can show governance, audit or procurement teams that recovery works, not only that backups run.

Who decides in an incident

Who can request and approve a restore is agreed in advance and written down, so recovery can start quickly without anyone guessing who decides.

Your keys, your control

Planned

We're building customer-controlled encryption for backup first: you manage the keys, approve every restore, and see every access logged.

Ask us where this stands for your deployment

What to prepare

You do not need all of this for a first conversation, but these are the answers a recovery plan is built from.

  • The systems and data in scope
  • How much data loss each system can tolerate
  • How long each system can be unavailable
  • Retention requirements, including legal ones
  • How often restores should be tested
  • Who approves a recovery

How an engagement can look

Illustrative examples show how an engagement can be shaped. They do not describe specific clients.

Illustrative exampleData protection

From untested backups to a recovery plan

The situation
A Crown corporation's backups run every night, but nobody has tested a full restore.
What Robson does
Robson agrees recovery point and recovery time objectives for each system, then schedules and records restore tests.
What changes
The corporation can show its governance and audit teams that recovery works, not only that backups run.

Review your data protection.

Tell us which systems you must recover and how quickly, and we will discuss the right protection scope.

Talk to our team Call 1-833-MY-EMILY

Or email sales@robsoninc.com