English
Nederlands
Deutsch
Disaster Recovery as a Service
Back to before it happened
Backup brings back your files. Disaster recovery brings back your business: standby infrastructure in Dutch and German data centres, a plan tested every quarter, and a team that runs it with you.
Rewind
Go back to a clean moment
Every restore point is immutable. Nobody can change or delete it, so there is always a version from before the attack.
Recover in isolation
A clean room for your systems
Restore points are scanned for malware, and systems start in an isolated recovery environment on a separate, clean network.
Safe in the EU
Your data securely stored
Your restore points are kept immutable in our Dutch and German data centres, ready for the moment you need them.
The next morning
Back to work
Critical workloads restored on a 4‑hour SLA, with a recovery plan that is tested every quarter.
Get a free DR assessmentIn short
What is disaster recovery?
Disaster recovery (DR) is the plan, the standby infrastructure and the team to get your systems running again after an outage, a ransomware attack or a site failure. Backup keeps copies of your data. Disaster recovery brings back whole systems, in the right order, within a time you agreed in advance.
- What it adds to backup
- Standby infrastructure and a tested plan to fail over whole systems
- Where it runs
- Data centres in the Netherlands and Germany, under EU law
- How it's tested
- Automated failover tests every quarter, with evidence for your auditor
- Who runs it
- Mindtime, with personal support in Dutch, German and English
DR vs backup
Backup restores data. DR restores operations.
A restored file doesn't help if the server it lives on is gone. That is the gap disaster recovery closes.
| Backup as a Service | Disaster Recovery | |
|---|---|---|
| What it protects | Data: files, mailboxes, databases, VMs | Systems and the way they work together |
| After an incident | You restore what you need | Systems fail over to standby infrastructure |
| Measured by | How much data you can lose (RPO) | How long you're down (RTO) and how much data you lose (RPO) |
| Testing | Every backup job checked | Full failover tested every quarter |
| Built for | Deleted files, lost mail, a corrupted database | Ransomware, site outages, hardware failure |
Disaster recovery builds on backup, so most businesses need both. Backup as a Service
RTO and RPO
Two numbers define your recovery
We set both with you, per system, before anything is deployed. Your plan is built around them, and every test checks them.
Recovery point objective (RPO)
How much work can you lose?
The time between your last restore point and the incident. Anything created in that window has to be redone.
Recovery time objective (RTO)
How long can you be down?
The time between the incident and systems running again. Your most critical systems get the shortest RTO.
How it works
From assessment to a tested failover
You don't get a self-service tenant and a manual. Every deployment is scoped to your systems, your RTO and RPO, and the rules you answer to.
- 01
Free, no obligation
Assess
A certified engineer maps your systems, their dependencies and the order they need to come back in, and agrees RTO and RPO targets with you.
- 02
Guided
Deploy
We deploy the agents and prepare standby infrastructure in our Dutch and German data centres, without disrupting your work.
- 03
Typically within 10 days
Prove
Your first test failover is run and validated, so you know the plan works before you ever need it.
- 04
Every quarter
Test and maintain
Automated DR tests check that your virtual machines boot from the recovery copy, and you get the results.
When ransomware hits
Recover without bringing the attack back
Restoring straight into an infected network just starts the attack again. This is how we bring you back cleanly.
- 1
Pick a clean point
From immutable restore points that nobody can change or delete.
- 2
Scan before restore
Restore points are checked for malware before anything starts.
- 3
Start in isolation
Systems come up in an isolated recovery environment on a separate, clean network.
- 4
Return when it's safe
Critical workloads are restored on a 4‑hour SLA, and go back into production once your environment is clean.
Testing and evidence
A plan you can prove
An untested recovery plan is a hope. Regulators and auditors ask for evidence, and you get it automatically.
Every quarter
Drills with signed evidence
Automated DR tests confirm that virtual machines boot from the recovery copy. The results are documented and signed, ready for your auditor.
NIS2 · Article 21(2)(c)
Business continuity, covered
NIS2 requires backup management, disaster recovery and crisis management. Mindtime covers the technical recovery layer. Governance and incident reporting remain yours.
NIS2 complianceISO 27001 · NEN 7510
Independently audited
Security controls, access management and incident response are audited every year, including the Dutch standard for health data.
ISO 27001 certificate (PDF)
Disaster recovery guides
Plan your recovery
Practical guides on the questions that come up when you build a recovery plan.
- 01What is disaster recovery?DR vs backup explained, and when you need which.
- 02RTO and RPO planningHow to set recovery targets per system, without overpaying for the ones that can wait.
- 03Failover testing and runbooksWhat a good DR test covers, and what belongs in your runbook.
- 04The cost of downtimeA simple model to put a number on an hour of downtime for your business.
- 05What disaster recovery costsAsk for a price based on your own systems and recovery targets.
- 06Ransomware recovery timelineWhat happens, hour by hour, after an attack is discovered.
- 07Should you pay the ransom?The questions to ask before anyone opens a negotiation.
- 08Proxmox backup and recoveryProtecting and recovering Proxmox workloads.
FAQ
Common questions
What is disaster recovery as a service (DRaaS)?
Disaster recovery as a service is the plan, the standby infrastructure and the team to get your systems running again after an outage, a ransomware attack or a site failure. Mindtime runs it for you from data centres in the Netherlands and Germany.
What is the difference between backup and disaster recovery?
Backup keeps copies of your data so you can restore files, mailboxes or databases. Disaster recovery brings back whole systems, in the right order, on standby infrastructure, within a recovery time you agreed in advance. Most businesses need both. Read about Backup as a Service.
What are RTO and RPO?
The recovery time objective (RTO) is how long a system can be down. The recovery point objective (RPO) is how much recent data you can afford to lose. We set both with you, per system, before anything is deployed. RTO and RPO planning.
How often is the disaster recovery plan tested?
Every quarter. Automated DR tests check that your virtual machines actually boot from the recovery copy, and you receive the results as evidence for your auditor.
How long does it take to get started?
A certified engineer maps your systems and dependencies, deploys the agents and validates your first test failover, typically within 10 days.
How does Mindtime recover from ransomware?
We pick a clean restore point from immutable backups that nobody can change, scan it for malware and bring systems up in an isolated recovery environment on a separate, clean network. Critical workloads are restored on a 4‑hour SLA.
Does disaster recovery help with NIS2?
Yes. NIS2 Article 21(2)(c) requires business continuity measures such as backup management, disaster recovery and crisis management. Mindtime covers the technical recovery layer and produces the test evidence. Governance and incident reporting remain your responsibility. See NIS2 compliance.