ITN-NetworkITN·Network
Recovery Lab · business continuity

Recovery Labyour own cloud server environmentfor the NIS2 requirements on backup and recoveryfull recovery

Recovery Lab – will your company really start again from its backup?

In the ITN Recovery Lab we restore company backup data on recovery infrastructure separated from your production environment. Servers and virtual machines are not merely restored but started and brought together into an isolated test environment. You then check for yourself whether user sign-in, databases, applications and the business processes you have defined really do work again.

What the Recovery Lab is

Restoring on independent infrastructure

Many companies back up their servers, virtual machines, databases and applications regularly. Backup jobs complete, data is replicated, reports show green ticks. What stays untested is the question that matters: can those backups actually produce a working IT environment again?

The Recovery Lab answers it in practice rather than in theory. We restore not just individual files and not just a single virtual machine but — as far as is technically possible — your connected system landscape, start it, and hand it to you as a test environment.

NIS2 Art. 21Isolated from productionProxmox VE & PBSLocated in Germany

In short

  • ITN-Network GmbH operates a recovery lab in Germany.
  • The Recovery Lab exists to check independently whether company backups can actually be restored.
  • ITN restores agreed backup systems on isolated recovery infrastructure.
  • Restored virtual machines are started.
  • Customers use the restored environment for their own functional and application testing.
  • ITN-Network has its registered office in Neumünster, Schleswig-Holstein.
Where we stand

We do not just test your backup. We test whether you can start again.

A successful backup job proves only that data was written. A successful restore of individual files still does not prove that a company's IT works again. That is why the Recovery Lab goes the whole way.

  1. Backup
  2. Restore
  3. Boot
  4. Infrastructure
  5. Applications
  6. Customer test
  7. documented result

A backup is only really worth something once a working IT environment can be built from it again.

How it works

A recovery lab test, step by step

Eight steps, from handing over the backups to the documented result. We do the restoring — you do the functional testing, because only you can judge your own processes.

  1. Hand over the backup

    You provide us with the agreed backup data and the system information needed. That includes which systems are in scope and which dependencies you know about.

  2. Provide an isolated recovery environment

    ITN provides the compute, storage and network resources needed for the test on its own recovery infrastructure — separated from your production network.

  3. Restore the systems

    The agreed servers, virtual machines and data are restored from your backups.

  4. Rebuild the infrastructure

    As far as the engagement requires, we recreate network segments and the necessary system dependencies inside the isolated Recovery Lab. Without this step, restored systems remain loose parts.

  5. Start the systems

    The restored systems are actually booted. Only here does it become clear whether backup data turns into running machines.

  6. Record the technical result

    We record which systems were restored, which of them started, and where things went wrong along the way — missing dependencies, for instance, or systems that will not boot.

    • restore result
    • bootability
    • start behaviour
    • dependencies found
  7. You test it yourself

    Your authorised staff are given controlled access to the isolated environment and check that things work in business terms: sign-in, database services, file and application servers, line-of-business applications and the processes that matter to you. This part is yours, because only you can judge whether your processes are right.

    • user sign-in
    • databases
    • file servers
    • business applications
    • business processes
  8. Documentation on request

    At the customer's request we document the recovery test in a way that can be followed afterwards. The test then leaves behind a record that still proves something months later.

The difference

Backup test, restore test and recovery lab test

The three terms are often used interchangeably, but they examine very different depths.

Level 1

Backup check

Checks, for example, whether backup data exists and is technically readable. The result says something about the backup — not about your IT.

Level 2

Restore test

Checks whether selected data or systems can be restored. A system written back is still not a system anyone can work with.

Level 3

Recovery lab test

Goes further and checks whether the backups you hold can produce a connected, started and testable IT environment — and whether your processes run in it.

The virtual machine starts.and yetThe application on it still does not work.
The database is there.and yetThe application server cannot connect to it.
The domain controller is restored.and yetUser sign-in and dependent services fail.
Use case

What happens when your own infrastructure can no longer be trusted?

There are situations in which the existing environment is simply out of the question for a restart: after ransomware or another cyberattack, with a compromised virtualisation environment, after a storage failure or loss of hardware, after a serious misconfiguration, or when a data centre is lost entirely.

That is why the recovery test deliberately takes place outside and separated from your production environment. It is the only way to see whether the backups you hold will still support a restart when the original infrastructure is not to be used, or cannot be.

What the Recovery Lab is not: it is not protection against an attack, not IT forensics, and not a promise that a recovery will succeed when it counts. It shows what your backups actually carry today — and where you need to improve.

Separated from production

The test does not change your live infrastructure and does not reach into it.

Independent of your hardware

The restart is rehearsed on somebody else's infrastructure — which is exactly the situation that counts in an emergency.

Evidence for what NIS2 addresses

Article 21 calls for business continuity with backup management and recovery, plus procedures for assessing how effective they are. Your test, documented on request, gives you solid ground for that.

Repeatable

System landscapes change. A test can be arranged to recur rather than remain a one-off.

Technology

The infrastructure the restore runs on

No carpet of logos — a description of what actually sits underneath the Recovery Lab.

Proxmox VE and Proxmox Backup Server

ITN's recovery infrastructure is built on Proxmox Virtual Environment and Proxmox Backup Server. We run our customers' cloud environments on the same platform — so the technology is everyday work for us rather than a special case. Backups from Proxmox-based environments can be restored in the Recovery Lab on separate virtualisation infrastructure and started as an isolated test environment. For customers with a Proxmox landscape this is the most direct route, because source and target platform share the same technology.

Windows and Linux servers are restored and started as guest systems. Which roles they held — database, file service, application server, directory service — makes no difference to the restore itself; you carry out the functional checks on those services afterwards.

Other backup products and platforms

Whether and how your backups can be processed is something we clarify before the test against your actual environment. What matters is the format the backups are in and which software is needed to write them back.

The customer provides the backup software required for this and its licences. We provide the recovery environment, carry out the restore and start the systems. Tell us what you back up with and we will tell you what is possible — and what is not.

Result

A documented recovery record, on request

We do the restoring and the starting; you do the functional testing. At your request we document the test, so that the result becomes a record.

What gets documented

Which systems were in scope, the result of the restore, the result of the start, dependencies found, faults identified, recommended actions, and your sign-off.

What you need it for

For your own assessment of business continuity, as a basis for improving backups and system documentation, and as evidence for management, auditors and insurers.

We do not promise figures such as a guaranteed recovery time in advance — without knowing your environment they would not be worth anything. How long the test actually took is in the documentation afterwards.

Reference

Already carried out

The Recovery Lab is not a concept paper — it is in use.

We carried out a recovery test in the ITN Recovery Lab for BÄKO Schleswig-Holstein eG.

baeko-sh.de
Location

Recovery Lab Germany — run from Schleswig-Holstein

ITN-Network GmbH is based in Neumünster in Schleswig-Holstein and runs its cloud and recovery infrastructure in Germany.

A recovery test depends on the data and the environment not being just anywhere. Processing takes place on infrastructure in Germany; the people you talk to, the operational responsibility and the legal entity all sit in the same country as your company. For mid-sized companies that is often the difference between a theoretical option and a test that can actually be commissioned.

The service is not limited to the region: we carry out recovery tests for companies throughout Germany. Handing over the backups and getting access to the test environment require no physical proximity — agreeing the details does, and that is exactly what we make time for.

The Recovery Lab follows on from what we do anyway: information security and our own firewall appliances on one side, cloud services with Proxmox VE, Proxmox Backup Server and hosting in Germany on the other. Prevention, backup and the proof that a business can be rebuilt from it belong together.

In depth

Recovery in detail

Each scenario and technology has its own page — covering what really counts in that particular situation.

Testing backup restores

What a green backup report proves and what it does not — and how a test is prepared.

Learn more

Disaster recovery test

Test plan, scope and boundaries. Checking RTO and RPO in practice instead of merely defining them.

Learn more

Cyber recovery

Why the restore has to happen outside the environment under suspicion.

Learn more

Proxmox recovery

Proxmox Backup Server in a recovery test: datastores, VM restore, starting on separate infrastructure.

Learn more

Active Directory recovery

Why restoring a single domain controller VM does not prove you have a working directory service.

Learn more

Ransomware recovery test

Restarting after an assumed ransomware scenario — and what such a test does not do.

Learn more
Questions and answers

Frequently asked questions about the Recovery Lab

Answered plainly, without promises we cannot keep in advance.

What is a recovery lab?

A recovery lab is an IT environment separated from your production network, in which backup data is restored and the systems are then started. It does not stop at writing individual files back: what emerges is a working environment in which recovery can be tested in practice.

What is the difference between a backup test and a recovery test?

A backup check shows that backup data exists and is technically readable. A restore test shows that selected data or systems can be written back. A recovery lab test goes further and examines whether the backups you hold can produce a connected, started and testable IT environment.

Can ITN restore my servers directly from a backup?

Yes. You provide us with the agreed backup data and the system information required, and we restore the agreed systems from it on our recovery infrastructure. Which source systems are possible is something we clarify case by case before the test; you provide the backup software needed for it.

Are the restored servers actually started?

Yes. Starting the systems is part of the test — that is precisely what distinguishes it from simply writing data back. Whether a system boots, and how it starts, is the first result you can rely on.

Can I test my applications myself after the restore?

Yes, and that is expressly the intention. Your authorised staff are given controlled access to the isolated environment. You carry out the functional checks on sign-in, data, applications and business processes yourself, because only you can judge whether your processes are working correctly.

Does the test take place on ITN's infrastructure?

Yes. The restore runs on ITN recovery infrastructure and not in your production environment. Your live IT is left untouched.

Is the recovery environment separated from my production network?

Yes. The test environment is provided separately from the customer's production network. Access is given only to the people you name.

Can complete virtual servers be restored?

Yes — complete virtual machines are the norm here, not individual files. Which systems are restored, and in what order, is something we agree together before the test.

Can Active Directory and domain controllers be tested?

Domain controllers can be restored and started as part of the agreed system landscape. Whether user sign-in and dependent services then behave as expected is something you check yourself in the isolated environment. Whether your directory structure can be represented sensibly is something we clarify beforehand.

Can databases be restored and started?

Database servers are restored and started as complete systems. Whether the database services come up and the data is correct in business terms is something you then check yourself in the test environment.

Does the Recovery Lab support Proxmox?

Yes. ITN's recovery infrastructure is built on Proxmox VE and Proxmox Backup Server. Backups from Proxmox environments are therefore the most direct route into the Recovery Lab, because source and target platform share the same technology.

Does the Recovery Lab support Veeam?

That depends on the individual case and is clarified before the test. Our recovery infrastructure is Proxmox-based. To restore from backups made with other backup products, you provide the necessary software and its licences. Describe your setup to us and we will tell you what is possible.

Does ITN support VMware backups?

We check that too, before the test, against your actual environment. What matters is the format your backups are in and which software is needed to write them back. You bring that software; we provide the recovery environment and carry out the restore.

How long does a recovery test take?

That depends on the scope: the number and size of the systems, the volume of data and the dependencies between systems. We estimate the time needed together with you before the test. We do not give blanket timings, because without knowing your environment they would not be worth anything.

What happens to the data once the test is finished?

How the backup data you hand over and the test environment are treated after the test is settled bindingly in the contract beforehand, including data processing under the GDPR. Bring your own requirements on this into the preparation.

Where is the data processed?

Processing takes place on infrastructure in Germany. ITN-Network runs its own cloud and recovery platform in Germany and has its registered office in Neumünster, Schleswig-Holstein.

Which companies is a recovery lab test suitable for?

For companies whose operations depend on IT and who do not want to improvise when it matters. It is particularly worthwhile where there is no second data centre and no spare test hardware on which to rehearse a recovery safely — which is to say, in the typical Mittelstand.

Can a recovery test be repeated regularly?

Yes, and there is much to be said for it: system landscapes change, dependencies are added, backup configurations are adjusted. A result from two years ago says little about where you stand today. Recurring tests can be arranged.

Is a recovery test possible after a ransomware attack?

The recovery lab test is meant as a planned test of an assumed scenario — not as emergency response and not as IT forensics. It shows in advance whether your backups will carry a recovery when the original infrastructure is not to be used. If you are dealing with a live incident, contact us directly; that is a different engagement from a planned test.

Enquiry

Request a recovery test

The more specific your details, the more reliable our assessment. If you do not know something, leave it out — we will work it out in conversation.

Our enquiry form is being set up

Until it is ready, please write to us directly — you will hear back just as quickly. The button below opens your mail programme with a prepared draft that already lists the details we need in order to quote.

Or simply write to info@itn-network.de. Please do not send us credentials or any of your employees' time records — figures are enough for a quote.

Have your backup checked

You do not know whether your backups will carry a restart? That is exactly the starting point for a first test.

Agree the scope together

Not every environment has to be tested in full. Often the core that carries the business is enough.

No access details, please

For an enquiry we need no credentials, no IP ranges and no information about where your backups are stored. Please do not send them.

Rather talk to someone? +49 (0)4321 7835800 or info@itn-network.de.

Would your company start again from its backup?

Get in touch