HomeCloud backupOn-site backupDisaster recoverySMBExpertiseContact

Disaster recovery that actually holds up

A documented business continuity plan is only useful if it's been tested. Measured RTO and RPO, validated failover scenarios.

The reality of DR

Backup is half the work.

A backup without a documented restore plan is like having a spare tire with no jack. When the fire or the ransomware hits, you discover it takes 3 weeks to rebuild instead of 3 hours.

Our approach to DR: we define with you the RTO (how long until you're back up) and the RPO (how much data you're willing to lose, at most), then we design the infrastructure and the procedure to meet those targets.

We test periodically (yearly at minimum, more often for critical industries) — not just the backups, but the entire plan: who calls whom, where you reconnect, how you prove to the team that you're back.

DR vocabulary

  • RTO — Recovery Time Objective: acceptable downtime
  • RPO — Recovery Point Objective: acceptable data loss (e.g. 1h)
  • BCP — Business Continuity Plan (the document)
  • DRaaS — DR as a Service (rented standby infrastructure)
  • Failover — switching over to the secondary site
Our approach

From audit to the yearly test.

Initial audit

We identify critical systems, their dependencies and the business impact of an outage scenario by scenario.

Custom RTO/RPO

Not an arbitrary number: we set it with you based on your tolerance and your budget.

Documented plan

Procedures, contacts, step order, failover scripts. Accessible out-of-band (paper + USB stick).

DR infrastructure

Either DRaaS with a cloud provider, or a physical secondary site depending on your needs.

Periodic tests

Yearly at minimum. We simulate a complete scenario and measure the actual RTO achieved.

Team training

Your employees know what to do in a disaster — not just the IT team.

Other solutions.

Can your SMB survive a disaster?

Free audit of your current DR readiness. Honest, no pressure.