Specialists in backup & recovery
How we workAbout usSupport ↗
ENNL
IMMUTEC
HomeDisaster recovery

Disaster recovery

Your servers may be down.
Your plan should be ready.

Give critical systems somewhere to run when production is unavailable. Our specialists coordinate backup-based recovery on site or in our data centre, and the agreed return to your source environment.

Discuss this solution All solutions

See how it works

From outage to recovery.
All the way back to production.

Recovery is a sequence of decisions and actions. We own the agreed work through the return.

Follow the process. Choose a step.

01 / 04

Choose the recovery point

When production is unavailable, we assess the available backup points, dependencies and recovery priorities. The recovery point determines the potential data gap.

02 / 04

Start the recovery systems

We start the supported systems in the agreed recovery environment, with the resources and IP/VLAN connectivity they need. Booting is one step; application checks follow.

03 / 04

Keep the business working

Validate the required services and run in the recovery environment. The source environment is prepared for a planned return.

04 / 04

Synchronise and return

When the source is ready, coordinate the final DR shutdown and backup, synchronise the final changes to the source, then start and validate production. The cutover is planned with you.

For the person accountable

Your business has a planned place to run during an outage, a team to carry out recovery and a coordinated route back.

For the engineer
  • RPO is the acceptable data gap; RTO is the target time to restore service. Agree both against workload dependencies and available capacity.
  • Confirm supported source and target hypervisors, IP/VLAN continuity, boot order and application validation.
  • Failback includes a planned interruption: coordinate final DR shutdown, backup, synchronisation and source startup.
Discuss the technical requirements

Illustrative backup-based DR sequence. RPO, RTO, capacity, connectivity and the failback cutover are agreed for your environment.

The problem we help you solve

The backup is available.
Where does the business run?

Restoring a virtual machine is one part of the job. Usable recovery also needs capacity, network connectivity, application dependencies and people who can coordinate the work.

01

A place to recover

Start supported recovery VMs on the on-site backup server or in our private data centre environment.

02

A connection to your business

Plan the IP and VLAN continuity needed for recovered systems to rejoin the right network.

03

A route back home

Include synchronisation and a coordinated return to production in the recovery plan.

What the service makes possible

Built for the real
recovery environment.

Local or data centre execution

Choose the recovery location around the outage scenario and your agreed service.

Cross-hypervisor recovery

Recover virtual machines across supported hypervisor environments. We confirm the source and target combination.

IP & VLAN continuity

Re-establish the required network presence so recovered systems can communicate with the client environment.

Scalable recovery resources

Plan and allocate the compute and capacity needed for the selected workloads.

Protected recovery points

Run recovery systems while preserving the immutability of the underlying backups.

Managed failback

Synchronise changes from DR back to the prepared source environment and coordinate startup and validation.

Recovery is a complete journey

Back up. Recover. Run.
Then return safely.

  1. 01

    Protect

    Create the agreed backup recovery points.

  2. 02

    Assess

    Select the appropriate point and recovery plan.

  3. 03

    Run in DR

    Start systems on site or in our data centre.

  4. 04

    Return

    Synchronise changes and restart production.

Failback belongs in the plan from day one.

When the source environment is ready, we coordinate the final DR backup and shutdown, synchronise the required changes back to the source and start the systems there. The cutover and validation are planned with you.

Recovery starts from an available backup point. Data loss and time to service depend on backup frequency, system startup, dependencies, capacity and the incident scenario.

Understand backup, DR and failback

Good questions

Clear answers.
Before you commit.

Is this continuous replication or zero data loss?

Recovery uses available backup points. The backup interval and service design determine the recovery point objective. We do not describe backup-based recovery as a universal zero-data-loss service.

Is recovery as quick as booting a VM?

VM startup is one part of recovery. Backup selection, capacity, connectivity, application dependencies and validation also affect when the business can work again. These are included in the planning discussion.

Can we test without affecting production?

We can agree a recovery test and an isolated scenario suitable for your environment. The test scope, connectivity and acceptance criteria are defined in advance.

Let’s make it concrete

Let’s make the scope clear.

Tell us about your environment and the outcome you need. We’ll agree coverage, responsibilities and the next practical step.

Discuss this solution Or call +31 (0)85 482 3400