RTO and RPO per system
Each system gets two figures: how long it may stay offline and how much data you can bear to lose. Everything else is derived from them.
Sooner or later something will fail. What matters is how quickly the business is working again. So we open with three questions: how long can each system be unavailable, how many hours of data can you afford to lose, and who does what during the first thirty minutes? Backup, monitoring and failover are then sized to those answers, never the other way round.
Six building blocks. The first is pure arithmetic. The remaining five are scaled to its results, so you never pay for more resilience than the business genuinely needs.
Each system gets two figures: how long it may stay offline and how much data you can bear to lose. Everything else is derived from them.
A fixed schedule and version history, one copy away from your premises and one immutable copy. Every month we restore a sample into an isolated environment.
Servers, Microsoft 365, internet lines, disk space, certificates and services are watched day and night. The alert reaches us before your staff notice anything.
A backup line from a second provider that switches over automatically and, for critical systems, a replica in a data centre ready to take the load.
We configure the UPS to shut servers down cleanly and track battery health. When a disk or battery needs replacing, we talk your local supplier through the swap.
A written disaster recovery plan: start-up order, named owners, phone numbers and how you keep customers informed while a system is down.
Five incidents we meet again and again. Each needs its own line of defence, and none of them can stand in for another.
Answered by backup and a replica. The most frequent incident and the simplest to plan for. Your supplier swaps the part, we handle the restore.
Answered by a copy the attacker cannot reach. Current strains hunt for backup files and encrypt them along with everything else, hence an immutable copy behind separate credentials and MFA.
Answered by long version history. A vanished SharePoint or file-server folder is often spotted weeks later, when yesterday's backup is no help at all.
Answered by a second provider. Two lines from one carrier frequently share a cable route and fail together. For many offices a 5G connection is a sufficient standby.
Answered by a UPS and orderly shutdown. Losing power abruptly does a database more harm than the outage itself.
A backup only counts once it has been restored. When we take over a new environment we regularly find jobs that have failed for months, backups of the wrong folder or an encryption key nobody in the building still knows. A test restore usually takes one working day and tells you exactly where you stand.
The question is not whether backups exist but when one was last restored and how long that took. Begin with a test: we take your most recent copy, bring it up in a separate environment and time it. The result either confirms your set-up or exposes the weak link, and both outcomes are worth knowing.
That depends on the figures you need. Being back within a working day is inexpensive. Being back within an hour calls for a warm standby in another data centre and costs more. So we calculate tolerable downtime per system first, and it often turns out that half of them are perfectly served by the cheaper model. A one-off test restore can be booked at DKK 895 per hour excl. VAT.
Our engineer does, over secure remote access and within the response time in your agreement: 15 minutes on Premium, 1 hour on Standard and 4 hours on Basis. With 24/7 support the duty line is staffed overnight too. If recovery needs physical hands, say a new power supply, we guide your caretaker or local supplier step by step. The plan is written so that one of your own people can follow it as well, and you keep the copy.
Yes, that is precisely what the test restore is for. Each month we recover a sample of data into an isolated environment and record the time. Once a year we recommend a tabletop exercise with management and key staff, walking through a scenario together. It quickly reveals where plan and reality have drifted apart.
Closely. NIS2, in force in Denmark since 1 July 2025, requires business continuity, backup management and crisis handling among other things. If you are in scope, the recovery plan and the log of test restores become part of the evidence you show the authorities.
We review your backup set-up, restore a copy and measure how long each system really takes to come back.
Thank you for getting in touch
One of our consultants already has it. Expect a reply within the working day; anything urgent goes straight to an engineer.
That city is not on our list. Check the spelling or pick the nearest larger town.