Skip to content
Backup & recovery

A backup that has never been tested is not a backup. It is hope.

We make sure your data is in more than one place, that restores are actually tried out regularly and that you know in advance how long you will be down if something goes wrong. Agreed, tested and on paper.

Hard drive for backup storage
Microsoft 365 included
Mail, OneDrive, SharePoint and Teams backed up too.
Tested restores
Recovery is practised, not assumed.
Recovery times on paper
Agreed with you in advance, per system.
A recovery plan
That someone other than us can follow too.

What backup and recovery means

Taking a backup is the easy part. What counts is that after a failed server, a ransomware attack or an accidentally deleted folder, you know how long it takes before you can work again, and how much work you would have to redo in the worst case.

In practice: together we decide per system how much data loss is acceptable and how quickly it has to be running again, we keep at least one copy that cannot be changed or deleted, we test restores to a fixed schedule and we write a recovery plan that someone other than us can follow too.

The 3-2-1 principle

Three copies, two types of storage, one out of reach

Not a statistic, but a rule that has been the basis of a good backup for years. That way one incident never hits all your copies at once.

3

Three copies of your data

Your working data and at least two backups. If one copy is lost, there are still two.

2

On two types of storage

For example a local backup server and cloud storage. A fault or error in one system does not affect the other.

1

One copy outside your building

Encrypted and, where the platform allows it, immutable: during the retention period nobody can change or delete it, not even with stolen admin rights.

Recovery time in plain language

Two questions decide what your backup should look like. We answer them together, per system, before anything goes wrong.

How much work can you afford to lose?

That is called the RPO. If your accounts are backed up every four hours, in the worst case you lose the last four hours of work. For one system a day is acceptable, for another it is not.

How long can you be down?

That is called the RTO: the time until a system is running again. Your ERP or till system needs something different from the archive of five years ago.

What we agree, we test

A recovery time on paper only means something once it is met in a test. If it is not, we adjust the setup and test again.

What our backup and recovery covers

Checked every working day
At the centre
Your data

Everything your business needs to work, stored more than once and demonstrably restorable.

Servers & virtual machines

Full images, quick to restore.

Files & shared folders

From the file server to the NAS.

Microsoft 365

Exchange, OneDrive, SharePoint and Teams.

Databases & packages

Accounting, ERP and other business software.

Off-site copy

Encrypted and immutable where possible.

Recovery plan

Steps, priorities and contact persons, on paper.
If something goes wrong

From report to working again

A server that no longer starts, a deleted folder or an encrypted drive. This is how recovery goes from the moment something goes wrong.

Which systems come back first and who decides on your side is set out in the recovery plan in advance. In the moment, nobody has to work that out any more.

  1. 1
    Report

    You call, or the monitoring raises the alarm

    We see a failed backup or a server dropping out in our monitoring. If you notice first, report it to the service desk, or outside office hours on the emergency line.

  2. 2
    Assess

    We establish what is affected and what comes first

    Which systems and data are involved, which backup is the right one and what the recovery plan says must come back first. With ransomware we choose a copy from before the attack.

  3. 3
    Restore

    Restoring, from one file to a full server

    We restore a deleted folder as it was at a given moment. If a server fails, the latest backup can run temporarily as a virtual machine while the hardware is looked at.

  4. 4
    Check

    Checking together that everything works

    One of your colleagues tests the restored application before we close. Recovery is only done once work can really carry on.

  5. 5
    Afterwards

    A short report, and a better setup

    What happened, what we restored and how long it took. Where it can be faster or safer, we adjust the setup.

Engineer with a laptop next to server racks

Tested, not just configured

A backup is only worth something if you can actually restore from it. That is why we schedule restore tests and you get a report of each one.

For the technically minded

How it is set up

The details below are for IT managers and technical decision-makers. If that is not you, feel free to skip this.

Not sure what you are covered for today?

Three questions, two minutes, and a first picture of where your IT stands today.

Start the IT check

Questions we get

Microsoft makes sure the service stays available, but only keeps deleted items for a limited time. In case of an error or an attack, files can be overwritten too. A separate backup of Microsoft 365 is therefore advisable.

Also of interest
View all solutions

Let us look at how quickly you would be back today.

We go through your current backups and tell you honestly what would happen if you had to restore tomorrow.