Take work off your team
Daily backup management and checks move to us.
Backups that run every night, are checked every morning and can’t be deleted.
We back up your servers, VMs and databases to our data centre in Amsterdam. Every recovery point is locked as soon as it is written. Our engineers watch the jobs and do the restores.
What happens to your data every night, and why an attacker can't touch it.
Every backup we run lands in our own data centre in Amsterdam and is locked as soon as it is written. This is what that looks like.
01 / 04
Back up
Our software reads the changed blocks of your servers, VMs and databases, encrypts them and sends them to our data centre. SQL Server gets an application-consistent snapshot, so the database is usable after a restore.
02 / 04
Lock
Each recovery point is stored on our own storage (Ceph) and locked for the retention period you choose. Nobody can change or delete it before that date, not even with a stolen admin password. The only exception is a signed request from you, carried out by two of our engineers on site.
03 / 04
Withstand an attack
Ransomware usually goes after the backups first. Here every delete, overwrite or retention change is refused, and our on-call engineer gets an alert. Removing protected data early needs a signed request and two of our engineers physically in the data centre.
04 / 04
Restore and verify
We pick a clean recovery point with you and restore it, while the original stays locked. Afterwards we compare checksums of the restored files with the backup, so you know exactly what came back.
In short
Even if your production servers are encrypted, your recovery points are still there and nobody can remove them. Our team runs the backups and the restores.
Technical detail
- Backup frequency and retention per workload. The newest recovery point determines how much data you could lose.
- Immutable copy on Ceph in our Amsterdam data centre, optional local copy for fast restores. Restores never modify the locked original.
- Integrity check after every restore: checksums of restored data against the source recovery point.
Example environment. Which workloads we back up, how often and for how long is set per customer.
A backup needs looking after once it is installed.
Environments change, disks fill up, people leave. Someone has to notice the failed job on Tuesday before you need that backup on Friday.
A copy outside your network
A locked copy in our own data centre, out of reach of anyone in your network.
Think about the restore
We agree retention, restore expectations and dependencies, so the data you get back is actually usable.
Built around your environment.
Servers, VMs and databases
Physical servers, Hyper-V and other virtual platforms, databases and cloud workloads. We confirm compatibility before onboarding.
Immutable recovery points
Every recovery point is locked for the retention period. Restores read from it but never change it.
Private cloud plus optional local copy
The protected copy lives in our Amsterdam data centre. A local copy speeds up everyday restores.
Integrity check after restores
We compare checksums of the restored data with the backup, so you know what came back is what went in.
Engineers who run it
Backup management, monitoring, checks and restores are done by our team.
Also need somewhere to run when the servers are gone?
Backup gives you recovery points. Disaster recovery adds the environment, capacity and plan to keep working during an outage.
Disaster recoveryFor management
Even after ransomware your recovery points are still there, and you get reports you can show your board and auditor.
For IT partners
Deliver it under your own name. We do the daily management and the restores.
How the partnership worksQuestions we get a lot
Something else? Call us on +31 (0)85 482 3400.
Can we keep a local backup?
Yes, a local copy can be added. The independent, locked copy stays in our data centre.
Does backup include disaster recovery?
No. DR, compute capacity, network continuity and failback are a separate part of the service. We agree what is included.
How do you choose frequency and retention?
Based on how much data you can afford to lose, what each workload needs and how far back you want to be able to go.
Let’s make the scope concrete.
Tell us about your environment and what you need. We’ll agree what is covered, who does what and the next step.