Talk to us
Menu

Services · Run

Backup and disaster recovery

Backups you have actually restored, and a written plan for getting systems back after a failure or attack.

A backup is only proven once it has been restored. We agree with you how much data each system can afford to lose and how long it can be down, then design backups to match: copies in another location, immutable copies that ransomware cannot encrypt, and run-books for bringing each system back. Then we test the restores and record the results.

What you get

  • Recovery point and recovery time targets agreed for each system
  • Backup policies for databases, files, servers, SaaS data and configuration
  • Offsite and immutable copies kept apart from production credentials
  • Step-by-step recovery run-books for each critical system
  • Scheduled restore tests with recorded timings and any problems found
  • A disaster recovery exercise report with fixes for the gaps it exposed

How it works

  1. 01

    Assess

    We list systems and data, check existing backups and agree how much loss and downtime each one can tolerate.

  2. 02

    Design

    We choose backup methods, retention, locations and a recovery site that meet those targets within your budget.

  3. 03

    Implement

    Backups are configured, encrypted and monitored, with alerts whenever a job fails or runs late.

  4. 04

    Test

    We restore real systems in an isolated environment, time the restore and update the run-books with what we learn.

Scope it now.

Answer a few questions and we prepare the email for you. Nothing is sent until you press send in your own email app.

Prefer to write freely? hello@clockborn.com

What needs protecting?
Do you back up today?
How long could your main system be down?
Roughly how much data?

Questions

What are RPO and RTO?

Recovery point objective is how much recent data you can afford to lose, such as the last hour. Recovery time objective is how long a system can be down. Together they decide how often to back up and how fast restores must work.

Does the cloud not back up our data already?

Cloud providers keep their platform running, but protecting your own data from deletion or encryption is usually your responsibility. A bad script, an accidental delete or ransomware on a connected account can reach cloud data too.

How often should restores be tested?

Critical systems deserve a test at least every quarter and after any major change. Less critical ones can be sampled less often. The schedule is written into the plan so tests happen even when nobody is worried.

Related services

Managed hostingYour applications hosted and looked after in cloud accounts you own, with patching, backups and costs handled.Managed securityDefensive monitoring of your systems, with alerts triaged and incidents contained by people who know your setup.Cloud setupA new cloud environment set up securely, with accounts, networks, access and costs organised from the start.Security hardeningServers, cloud accounts, devices and apps locked down against a recognised benchmark, with every change recorded.

Software it applies to

Backup and recoveryEncrypted, off-site backups and rehearsed recovery plans that bring systems back after a failure or attack.Storage softwareSoftware that stores, tiers and replicates your files and objects, so data stays available as it grows.Database systemsWell-designed, fast and recoverable databases for the applications and reports your business depends on.

Language · 42