SCNET · Enterprise IT · Ankara, Türkiye

Sanal Çekirdek

You can buy recovery as a service instead of a second data center.

DRaaS turns recovery capability from a capital item into a service. The decision is commercial rather than technical: build the second site, or buy the capability.

Infrastructure design is covered on the Disaster Recovery page under Services. This page is about the model itself: what you are buying, where responsibility begins, and how rehearsal works.

Own site or service

Building your own second site demands capital and continuous operational effort; a service model converts that into recurring cost but moves the responsibility boundary into a contract. The decision follows recovery objectives and rehearsal frequency.

  • Capital and operating load are compared in one table
  • Rehearsal frequency affects cost directly
  • Systems left out of scope are written down at the start
  • An exit scenario is defined in the contract

What is actually covered

Scope is the source of most later disputes. Which systems are protected to which objective, the data transfer window, and who does what during failover are itemized in a contract annex.

  • The protected system list ships with its objectives
  • Role allocation during failover is written down
  • Capacity commitments are checked against peak load
  • A test environment is provided separately from production

Rehearsal as a contract term

In a service model, rehearsal is the clause most easily skipped. How many times a year, at what scope and with whose participation is put on a calendar up front, and each rehearsal is reported with its measured duration.

  • The rehearsal calendar forms part of the contract
  • Each rehearsal reports its duration against the objective
  • Findings are allocated between provider and customer
  • Reports are usable in audit and insurance processes

Decision and communication

The failover decision stays with you. Who decides at which threshold, and how that decision reaches the provider, is written in advance; searching for a phone number during a crisis is not a plan.

  • Decision owner and deputy are defined by role, not by name
  • Two channels exist for reaching the provider
  • Customer and staff communication is planned separately
  • The failback decision follows the same discipline

How we work

  1. Identify critical systems and recovery objectives
  2. Compare an own site against the service model
  3. Write scope and role allocation into the contract
  4. Commit to a rehearsal calendar
  5. Revisit objectives after every rehearsal

How success is measured

  • The protected system list stays current with its objectives
  • The rehearsal calendar runs and is reported
  • Provider-side takeover meets the agreed objective
  • The decision and communication chain has been exercised

Frequently asked questions

Then what does the Disaster Recovery page cover?

Infrastructure design sits there: dependency mapping, replication technique and recovery order. This one covers the service model, the responsibility boundary and the rehearsal regime.

Should every system be covered?

It need not be, and usually should not. Scope is limited to critical services, and exclusions are documented with their reasons so nothing is a surprise during a crisis.

What if we change providers?

That is why an exit scenario is defined at the start: how data is retrieved, in what format it is handed back, and how long the transition takes are all in the contract.

Share your critical system list and recovery objectives; we will compare an own site against the service model in one table.

Let's compare the two models