A place to run
Recovery VMs start on the local backup server or in our data centre.
When your servers are down, they start in our data centre.
Your critical systems get somewhere to run when your own environment can’t be used. Our engineers start them from your backups, keep the network addresses the same, and move everything back when your environment is ready.
Your productionHyper-V, VMware, physical servers
runningbackup every night
Recovery pointsImmutable, in Amsterdam
lockedoutage: start here
DR environmentSame IP addresses and VLANs
standbyafterwards: changes go back
Your server room goes dark at 07:42. This is what happens next.
An example day: a Hyper-V cluster fails, the business keeps working from our data centre in Amsterdam, and in the evening everything moves back.
01 / 05
The site goes down
Both Hyper-V hosts stop responding and the ERP system, file shares and web application go with them. Our on-call engineer starts the DR plan and lets you know what happens next.
02 / 05
Start in our data centre
We pick the last clean recovery point and start the VMs from it in our data centre, domain controller first, then the database, then the rest. A VM from VMware can be started on Hyper-V; we check that combination with you beforehand.
03 / 05
Keep the same network
A tunnel extends your VLANs to the DR environment, so SQL01 is still 10.20.0.15. Laptops, printers and integrations don't need new settings. Once a test order goes through, people get back to work.
04 / 05
Run while the site is rebuilt
Your business runs from Amsterdam for as long as it takes. Everything people change is backed up there too, while your own servers are repaired or replaced.
05 / 05
Move back
In a cutover window we shut down the DR VMs, make a final backup and sync only the blocks that changed since the outage back to your site. Production starts again, we check it with you, and DR goes back to standby.
In short
When your own servers stop, your business has a place to keep working and a team that does the recovery. Coming back is part of the plan, not an afterthought.
Technical detail
- Recovery starts from a backup, not continuous replication: the backup interval sets your potential data loss (RPO).
- Network continuity by extending the required VLANs; recovered VMs keep their IP addresses. Source and target hypervisor combinations are checked during onboarding.
- Failback is planned: final DR backup, sync of changed blocks to the prepared source, startup and validation, with a short planned interruption.
Example scenario. Which systems, boot order, capacity and network setup apply is determined per customer. How much data you could lose depends on how often you back up.
Having a backup is not the same as having somewhere to run.
Restoring a VM is one part of the job. You also need capacity, network connectivity, application dependencies and people who coordinate the work.
The same network
Recovered systems keep their IP addresses and VLANs, so users and applications can find them.
A way back
Syncing changes and moving back to production are part of the plan.
Built for the real recovery environment.
Local or in our data centre
The recovery location depends on the type of outage and your service.
Across hypervisors
Virtual machines can be recovered on a different hypervisor than they came from. We confirm the source and target combination.
IP and VLAN continuity
Recovered systems keep their IP addresses and VLANs. A secure connection extends your network to our data centre, so nothing changes for users.
Scalable capacity
We plan and reserve the compute and storage your workloads need.
Locked recovery points
DR systems run from your backups without touching the immutable originals.
Managed failback
We sync changes from DR to your prepared environment and coordinate the start-up and checks.
Back up, recover, run, and then move back.
- 01
Back up
Recovery points are made and locked.
- 02
Decide
Pick the right recovery point and plan.
- 03
Run in DR
Systems start on site or in our data centre.
- 04
Move back
Changes are synced and production restarts.
We plan the way back from day one.
When your own environment is ready, we make a final backup in DR, shut the DR systems down, sync the changes back to your environment and start the systems there. You decide when the switch happens and you check the result.
Recovery starts from an available backup. How much data is lost and how long it takes depends on backup frequency, start-up time, dependencies, capacity and the kind of incident.
Backup, DR and failback explained Watch the demoFor management
The business keeps working during an outage, and you decide in advance which systems come back first.
For IT partners
Offer disaster recovery without building a recovery environment yourself.
How the partnership worksQuestions we get a lot
Something else? Call us on +31 (0)85 482 3400.
Is this continuous replication or zero data loss?
No. Recovery starts from your backups, so the backup frequency determines how much data you could lose. We don’t sell backup-based recovery as zero data loss.
Is recovery as quick as starting a VM?
Starting the VM is one step. Picking the recovery point, capacity, network, application dependencies and checks all affect when people can work again. We plan for all of it.
Can we test without affecting production?
Yes. We agree a test scenario in an isolated environment, with the scope, network and success criteria set in advance.
Is there a faster option?
Yes. With hot standby we keep a recovery environment ready at all times, so your systems run within minutes from the last backup. With standard DR we start the environment when it is needed.
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.