Data Protection and Continuity

Disaster Recovery Center: safeguard your business continuity during outages

Bring critical systems up in a second environment even if the primary environment goes down.

In brief

A Disaster Recovery Center (DR) lets critical systems run again at a second location when the primary data center or cloud environment becomes unavailable. Nanda Teknoloji defines your objectives (RTO and RPO), sets up replication, writes the activation plan and runs DR tests with you. Scope and goals are defined together according to your needs.

Who is it for?

  • CIO / CTO
  • IT Director
  • Information Security Manager
  • System Administrator
  • Procurement Manager

What problems does it solve?

  • Dependence on a single location and a high business impact from outages
  • A disaster plan that stays on paper and is never tested
  • Not knowing which system will come up in which order
  • Regulations requiring evidence of business continuity

Scope and approach

Business impact analysis

We classify systems by criticality and work out the cost of downtime and the objectives together.

Replication design

We design how data and systems will be copied to the DR environment and with what delay they will run.

Activation plan

We write step by step which system comes up in which order and under whose responsibility.

DR exercises

We validate the plan through regular tests and turn the results into improvement actions.

Failback

We also plan the controlled return process for when the primary environment is restored.

Integration with backup

Backup and DR solutions are handled as parts of a single design.

Architecture approach

  • Primary environment (data center / cloud)
  • Critical applications
  • Databases

Nanda

Disaster Recovery Center

  • Replication and activation
  • Regular DR exercises
  • Controlled failback
Systems in the primary environment are continuously copied to the DR environment; during an outage the activation plan runs, and once resolved a controlled failback is performed.

What we settle during design

For the right decision, we put the topics below in writing on every project. The list also works as a checklist when you evaluate vendors.

Disaster Recovery Center decision criteria
TopicQuestion to settle
Critical systemsWhich systems are in DR scope; what is the priority order?
RTO / RPOWhat are the acceptable downtime and data loss?
DR modelWhich standby model is suitable: hot, warm or cold?
Test frequencyHow often, in what scope and with whose participation is the DR exercise run?
DependenciesHow do the network, authentication and third-party integrations work in the DR environment?

Use cases

01

Critical business applications

Business continuity assurance for ERP, payment and customer systems.

02

Regulation and audit

Produce documented, tested evidence of the business continuity plan.

03

Recovery after ransomware

Restart systems in a controlled way in a clean environment.

How do we start?

  1. 1

    Discovery

    Together we clarify the current environment, goals and risks.

  2. 2

    Design

    We put the architecture, service level and migration plan in writing.

  3. 3

    Migration

    We migrate step by step, tested and with minimal downtime.

  4. 4

    Operations

    We take responsibility for monitoring, maintenance and incident management.

  5. 5

    Improvement

    We measure, report and keep improving the environment.

Disaster Recovery Center frequently asked questions

What is a Disaster Recovery Center (DR)?

It is the whole of infrastructure and processes that lets critical systems run again at a second location when the primary environment becomes unavailable.

What is DRaaS?

DRaaS (Disaster Recovery as a Service) means receiving disaster recovery infrastructure and processes as a service. Instead of building your own second data center, you pay for what you use.

Does backup replace DR?

No. Backup restores data; DR is designed to also guarantee how quickly the system will be running again.

How are RTO and RPO determined?

Through business impact analysis; the business cost of downtime and data loss is calculated for each system and the acceptable limits are written accordingly.

How often should DR be tested?

At least once a year for critical systems, and after changes. Frequency and scope are planned according to your risk appetite.

In which location will the DR environment be?

The location is chosen together during the design phase according to your data residency and network requirements.

Related solutions

Let's plan your critical systems together

Tell us what you need; our team will work out the right architecture and migration path with you.