Skip to content

Disaster Recovery: the worst-case scenario,
calculated to the minute

Disaster Recovery for the Private Cloud from data centres in Germany: 3 tiers from “Secured recovery” to “Asynchronous replication”. Billed per protected environment and month — a base fee plus a rate per protected gigabyte. The recovery point objective (RPO) dictates the state from which you resume work; the recovery time objective (RTO) dictates when. Both figures are guaranteed separately and apply only under one condition. Set below when disaster strikes and how much you are protecting: each tier then shows its times, its monthly cost and the condition currently in effect.

Restriction: The RPO of 15 minutes applies up to a change rate of 40 MB/s per datastore. Above this, the replication lag grows, and the actual recovery point is further back than committed.

Data loss (RPO)
15 min – 24 h
Recovery point: how many minutes of work an outage costs
Recovery time (RTO)
2 h – 8 h
Recovery time: how long it takes until the first functional response
Distance to the second location
from 150 km
Straight-line distance to the destination, minimum distance of each tier
Base from
€149.00$172.84
per protected environment and month, net

Select the day of the week and time of the incident, the protected capacity and the platform. Each of the three levels then shows the state from which you can continue working, when you will be reachable again, what it costs per month and which condition applies at that time.

The minutes are the guaranteed values of the tiers, the amounts are calculated using the same rates as the configurator — only the distances of the time lines are logarithmically compressed so that even the narrowest tier has a visible length.

Time of the incident

Day of the week
00:0023:45

In the daily window Mon–Fri 08:00–18:00: The “Secured recovery” tier also meets its time commitment here.

Incident Tuesday, 14:30

1 TB128 TB

The rate per gigabyte is calculated on exactly this amount; the base fee does not depend on it.

Platform

It determines which tiers are available to choose from and what the protected capacity is based on.

€$ per hour

Your assumption, our minutes: minutes × hourly rate. The calculation does not account for night hours or consequential costs.

  1. Secured recovery

    Nightly backup to a second EU region, restart on demand.

    €179.31$208.00

    net per month

    Base €149.00$172.84 + 4,096 GB × €0.0074$0.0086

    24 h data loss

    8 h recovery

    Last state
    Mo 14:30
    Incident
    14:30
    Available again
    22:30

    Condition: The restart uses free capacity in the target region. Without booked capacity reservation, the RTO commitment only applies Mon–Fri 08:00–18:00; outside this time, there is no guaranteed restart time.

  2. Pilot Light

    One standby host in the target region, replication every four hours.

    €567.82$658.67

    net per month

    Base €490.00$568.40 + 4,096 GB × €0.0190$0.0220

    4 h data loss

    4 h recovery

    Last state
    10:30
    Incident
    14:30
    Available again
    18:30
    Full performance
    20:00
    up to 90 min later

    Condition: A single host runs in the target region with around 25% of the productive capacity. Full throughput is only available after adding more hosts — lead time up to 90 minutes.

  3. Tightest tier on this platform

    Asynchronous replication

    Quarter-hourly block replication to a region in the same jurisdiction.

    €1,129.26$1,309.94

    net per month

    Base €990.00$1,148.40 + 4,096 GB × €0.0340$0.0394

    15 min data loss

    2 h recovery

    Last state
    14:15
    Incident
    14:30
    Available again
    16:30

    Condition: The RPO of 15 minutes applies up to a change rate of 40 MB/s per datastore. Above this, the replication lag grows, and the actual recovery point is further back than committed.

Net amounts per month. Equal distances on the timelines represent equal factors, not equal minutes; the times below are exact.

Tuesday 14:30, protected capacity 4 TB, 3 von 3 Stufen mit Zeitzusage.

The recovery point objective (RPO) states how much work is lost in an emergency. The recovery time objective (RTO) states how long it takes until the first functional response. Both figures only apply under one condition — and this is stated for each tier, not in the small print.

The replication interval is the reason why an RPO even has a number: there are exactly 15 minutes between two runs of tier Asynchronous replication, and if a failure occurs in minute fourteen, you lose those fourteen minutes.

The recovery time depends on a second condition that is not included in the number: the capacity in the target region. Secured recovery starts up on free capacity and therefore only keeps its time commitment during the day on weekdays. Pilot Light provisions a host and starts immediately — but with around a quarter of the production performance until further hosts are added.

Recovery

Logarithmic timeline · 5 min to 24 h

Recovery tiers: data loss and restart

INCIDENT← before · data lossafter · recovery →5 min5 min15 min15 min1 h1 h4 h4 h24 h24 hSecuredRecovery€149.00 socket$172.84 SockelRPO 24 hRTO 8 hReplication every 24 hSecond EU region, from 150 kmPilot Light€490.00 socket$568.40 SockelRPO 4 hRTO 4 hReplication every 4 hRegion in the same jurisdiction, from 150 kmAsynchronousReplication€990.00 socket$1,148.40 SockelTightest levelRPO 15 minRTO 2 hReplication every 15 minRegion in the same jurisdiction, from 150 km
  • RPO — Data loss window before the incident
  • RTO — Recovery after the incident
  • Tightest tier — shortest recovery, highlighted

Both halves of the axis are logarithmically compressed. Drawn linearly, the fastest tier would be a line: 15 minutes is one per cent of 24 hours. The compression comes at a price that should be stated here — equal distances mean equal factors, not equal minutes: the distance from 15 minutes to 1 hour is just as long as the one from 6 to 24 hours. Both quadruple the time; one costs 45 minutes, the other 18 hours.

Recovery point objective (RPO), recovery time objective (RTO) and price components per tier. Amounts are net; the rate per protected gigabyte is less than one cent and is therefore shown with four decimal places.

Recovery tiers compared
TierRPORTOReplication intervalTarget regionTests per yearBase fee per monthPer protected GB
Secured recoveryNightly backup to a second EU region, restart on demand.24 h8 hevery 24 hSecond EU region, from 150 km1€149.00$172.84€0.0074$0.0086
Pilot LightOne standby host in the target region, replication every four hours.4 h4 hevery 4 hRegion in the same jurisdiction, from 150 km2€490.00$568.40€0.0190$0.0220
Asynchronous replicationQuarter-hourly block replication to a region in the same jurisdiction.15 min2 hevery 15 minRegion in the same jurisdiction, from 150 km4€990.00$1,148.40€0.0340$0.0394

Limitation per tier

Secured recovery
The restart uses free capacity in the target region. Without booked capacity reservation, the RTO commitment only applies Mon–Fri 08:00–18:00; outside this time, there is no guaranteed restart time.
Pilot Light
A single host runs in the target region with around 25% of the productive capacity. Full throughput is only available after adding more hosts — lead time up to 90 minutes.
Asynchronous replication
The RPO of 15 minutes applies up to a change rate of 40 MB/s per datastore. Above this, the replication lag grows, and the actual recovery point is further back than committed.

Not every tier is available on every platform

Approval follows the technology, not the price. Pilot Light is missing from the certified SAP nodes: a standby host with around a quarter of the production capacity does not match the approved configuration. The certification applies exclusively to the delivered one.

Availability of the 3 recovery tiers on the four virtualisation platforms of the Private Cloud. Ticks and minuses each have their own name; the colour does not stand alone. · Table scrollable sideways

Recovery tiers per virtualisation platform
TierKVM PlatformManaged vSphereHCISAP Certified
Secured recoveryNightly backup to a second EU region, restart on demand.
Pilot LightOne standby host in the target region, replication every four hours.
Asynchronous replicationQuarter-hourly block replication to a region in the same jurisdiction.

Two amounts, two bases

A recovery tier costs a fixed base fee per protected environment and an additional rate for each protected gigabyte. The two amounts measure different things and are therefore shown separately — even where a single number would be more convenient.

Component 1 · per environment

Base fee

€149.00$172.84up to €990.00$1,148.40 per month

This pays for what is incurred regardless of the data volume: orchestration of the failover, the maintained runbook (the written step-by-step guide for recovery), the provisioned target environment and the recovery tests of the year. Two terabytes and twenty terabytes cost the same here, because the effort is the same.

The base fee is the starting price of this page: €149.00$172.84 net per month for Secured recovery — corresponding to €177.31$205.68 incl. 19% VAT.

Component 2 · per gigabyte

Rate on the protected capacity

€0.0074$0.0086up to €0.0340$0.0394 per GB and month

This rate pays for the second copy: transfer, occupied capacity at the destination and its redundancy. It grows with every protected gigabyte and is therefore the variable that actually controls the price of an environment — not every volume needs to be protected.

Four decimal places, because two are not enough: €0.0074$0.0086 rounded to two places would be €0.01$0.01, and the rate of the entry tier would thus be significantly too high in the table.

Which component drives the cost, and when

Up to a protected capacity of around 19.7 TB to 28.4 TB — depending on the tier — you pay predominantly for the procedure, not for the data. Only above this does the ratio reverse. This is the number that should be asked for first in procurement, because it decides whether an environment becomes cheaper with fewer protected volumes or not.

Both price components separately, plus the monthly total for three protected capacities and the point at which the capacity share catches up with the base fee. All amounts net. The rate per gigabyte is under one cent and is therefore shown with four decimal places. · Table scrollable sideways

Price components per recovery tier
TierBase fee per monthPer protected GBTotal at 1 TBTotal at 8 TBTotal at 64 TBParity from
Secured recovery€149.00$172.84€0.0074$0.0086€156.58$181.63Base fee 95%€209.62$243.16Base fee 71%€633.97$735.41Base fee 24%19.7 TB
Pilot Light€490.00$568.40€0.0190$0.0220€509.46$590.97Base fee 96%€645.65$748.95Base fee 76%€1,735.18$2,012.81Base fee 28%25.2 TB
Asynchronous replication€990.00$1,148.40€0.0340$0.0394€1,024.82$1,188.79Base fee 97%€1,268.53$1,471.49Base fee 78%€3,218.22$3,733.14Base fee 31%28.4 TB

The three example sizes are not quote tiers. Two of them are the minimum sizes of real datastore classes, the third is deliberately above all parity points — otherwise the table would only show base amounts and the second component would remain invisible. Recovery is billed in addition to hosts, licences, datastore and operations, not instead of them.

Open configurator3 tiers · base fee from €149.00$172.84 net

The rule determines what the copy protects against

Each tier binds its replica to a rule for the destination: a jurisdiction and a minimum distance. The rule is not a formality: it determines what event the copy actually protects against. A second location within sight will not survive an outage that affects the entire region.

Select tier — the map shows its permitted targets

Secured recovery: 1 valid location from dus1 — Frankfurt am Main (fra1, 183 km).

Origin dus1permitted target of the selected tierother locationpath to the nearest permitted targetEquirectangular projection around dus1; rings and distances calculated on the great circle from the location coordinates. The table below lists the same details in full.
Second location in the EU
For the furthest tier, binding to the European jurisdiction is sufficient; the distance protects against an event that affects an entire region.
Secured recovery— from 150 km
Location in the same jurisdiction
A change of location within the same jurisdiction leaves responsibility, reporting channels and the supervisory authority unchanged.
Pilot Light ·Asynchronous replication— from 150 km

Targets from dus1

Secured recoveryfrom 150 km

  • Frankfurt am Main (fra1): permittednext destination183 km
  • Helsinki (hel1): not permittedwithout Private Cloud1.502 km

Destination rule, distance limit and the locations that meet them from dus1 (Düsseldorf). This is checked as the crow flies from the location coordinates — the stricter check, because a fibre path is never shorter than the straight line. · Table scrollable sideways

Permitted destination locations per recovery tier
TierDestination ruleDistance limitPermitted from dus1Nearest destination
Secured recoverySecond location in the EUfrom 150 kmFrankfurt am Main (fra1, 183 km)fra1 · 183 km
Pilot LightLocation in the same jurisdictionfrom 150 kmFrankfurt am Main (fra1, 183 km)fra1 · 183 km
Asynchronous replicationLocation in the same jurisdictionfrom 150 kmFrankfurt am Main (fra1, 183 km)fra1 · 183 km
An open rack in a bright hall; a single compute node is mounted at the bottom, with empty rails above it up to the top frame.

A recovery time requires something to start at the destination. Pilot Light keeps one host warm for this; the remaining slots stay free until they are needed — which is why the tier starts immediately, but with around a quarter of the performance.

A recovery tier guarantees a point in time and a duration. It says nothing about which data actually arrives in the target region. This list is the answer to that, and the right column is the more important of the two.

What is replicated

The reference value is the protected capacity — the same amount on which the rate per gigabyte is calculated. Retained states are included, within the period of the respective datastore class — for the operational classes a maximum of 30 days.

Blocks of the protected datastores
Guest disks, configuration files and templates, provided they reside on a protected datastore. The replicated volume is exactly the volume billed for — there is no hidden surcharge for management data.
Snapshots as part of retention
The retention period of the datastore class also applies in the target region. It is the counterpart to replication: a replica protects against the loss of a location, a retained state against an error that was written to both locations.
Placement and network assignment
Which guest belongs in which segment, in what order it starts and what it depends on is detailed in the runbook and updated with every change. This is not a data stream, but a maintained document — and the part that stands out most often during a test.

What is not replicated

Six points where recovery typically gets stuck. None of these is a gap in the product — each is a decision that must be made on your side before it becomes apparent in an emergency.

Memory content
A restart is a cold start, at every tier. Write operations to storage are replicated, not the state of running processes. Whatever an application held only in memory is gone after the failover.
Local drives outside protected datastores
What resides on a host's local NVMe and does not belong to a protected datastore is not replicated. This particularly affects environments that were deliberately built without a shared datastore.
The management plane itself
vCenter or the cluster console are newly provisioned in the target region, not mirrored. In an emergency, a mirrored management plane would create two instances with the same claim to the same guests — the most expensive state imaginable.
Public addresses
A restart in another region runs under the addresses of that region. The switchover happens via the name service, unless you bring your own address ranges and announce them at the target location.
Everything outside the protected environment
Directory service, name resolution, time source, licence server, payment provider: whatever is not in the protected environment does not start up with it. Every such dependency needs its own answer before it stands out in the first test.
The difference between location loss and data error
A replication transfers every write operation, even the wrong one. A replica does not help against an accidentally deleted table, only a retained state from before does. Therefore, no tier on this page replaces a backup — each complements it.

Failover process

The takeover — in technical jargon failover, i.e. switching operations to the second location — runs in five steps, the sum of which results in the guaranteed recovery time: between 2 h and 8 h, depending on the tier. Individual steps deliberately do not have a minute specification: the sum is guaranteed, not its distribution.

  1. 01

    Trigger

    A failover is triggered by a designated person in your organisation, not decided by us — at every tier. You must weigh up whether the location will return before the recovery time of the tier has elapsed; this decision remains with you.

  2. 02

    Determine state

    Before starting, it is recorded which recovery point is actually present. It is usually more recent than the guaranteed RPO — the commitment is an upper limit, not a target value. This determination is the reason why a failover does not begin with the first click.

  3. 03

    Provision network

    Segments, firewall rules and name resolution are activated in the target region. Until then, nothing starts: guests that start before their network report errors that no one can subsequently distinguish from real ones.

  4. 04

    Start in order

    The guests start in the order of the runbook — databases before applications, applications before external access. The order is in writing because in an emergency it is not derived, but executed.

  5. 05

    Approve functionally

    The environment is considered failed over when your functional checkpoints have passed — not when all machines are running. Only with this approval does the recovery time guaranteed on this page end.

Failback process

The return process — failback, the return to the original location — is not an undo. It is a second switchover, with the same effort and the same care as the first. It runs in a maintenance window, meaning a previously agreed period, not during live operations.

  1. 01

    The target region remains primary

    After a failover, the environment continues to run there until the original location is fully capable again. A quick return to a just-recovered location is the second outage, not the end of the first.

  2. 02

    Replication in the opposite direction

    The changes that have occurred since the failover flow back to the origin. How this happens depends on the tier: everything from a full restore to a switchover without full synchronisation is represented — the procedure per tier is in the table below.

  3. 03

    Switchover in the window

    The actual return happens in an agreed maintenance window, not during live operations. It is short because the data synchronisation has already run at this point; what remains is a final delta and the reversal of the direction.

  4. 04

    Protection only applies again afterwards

    Between failover and completed return, the environment runs at a single location. During this time, there is no second copy and therefore none of the commitments on this page. This is the most important side effect of a failover — and the reason why a return is planned and not waited for.

How the changes from the target region return to the origin — wording from the catalogue, different for each tier, because the replication interval determines the return direction just as much as the outward direction.

Return procedure per recovery tier
TierReturn
Secured recoveryFailback as full restore, duration same as restart
Pilot LightFailback in the maintenance window, delta replication in the opposite direction
Asynchronous replicationSwitchover in the opposite direction without full synchronization, maintenance window 30 minutes

A recovery time of two hours that has never been tested against the clock says nothing about two hours — it says something about the operator's intention. That is why every tier includes a fixed number of tests per year, a testing procedure, and a criterion for when a test is passed.

The number of tests increases with the strictness of the commitment, and this is no coincidence: Secured recovery is tested 1 times a year because an eight-hour recovery window leaves plenty of leeway. A commitment of two hours leaves hardly any — it is proven 4 times a year or it does not apply. Failback is tested in the same test; a recovery with no way back is not a recovery, but a migration. Your procedure per tier is detailed in the section above.

Contractually scheduled tests per year, from the service catalogue. The failback procedure is in “Scope and process” and is not repeated here.

Scheduled tests per recovery tier
TierTests / year
Secured recovery1
Pilot Light2
Asynchronous replication4

Test process

The order is not arbitrary. Step three prohibits the specially prepared special state, step five prohibits the mere proof of start. Without these two blocks, a test tests itself and always passes.

  1. Step 01

    Date and window

    The date is agreed ten working days in advance and falls outside your closing and deadline periods. The test is announced, not a surprise — an unannounced test measures the readiness of people, not the recoverability of the environment.

  2. Step 02

    Isolated target network

    Recovery takes place in a network segment with no path to production. Same addresses, same names, no repercussions. The productive environment continues to run unchanged throughout the test; switching production is explicitly not part of the test.

  3. Step 03

    Startup from the latest replica

    The state that is already in the target region at the time of triggering is started. No specially taken snapshot, no prepared special state, no manual intervention on the replica before startup. What was not replicated is also not there in the test.

  4. Step 04

    Measurement against the committed figure

    The clock runs from the trigger until the first functionally correct response from the application — not until the startup process is complete. In parallel, the actual data state is determined and compared against the committed recovery point.

  5. Step 05

    Functional testing by you

    Login, a read and a write operation, a report or an interface query: you define the test points beforehand, and you execute them. Without this step, a test only proves that machines start.

  6. Step 06

    Dismantling and report

    The target environment is dismantled, the report is sent to you within five working days: measured recovery time, actual data state, every deviation from the commitment and, for each deviation, a measure with a deadline and named responsibility.

This is the structure of the report you receive within five working days

Each row compares a measured figure against a committed one. The structure shown uses the commitments of the strictest tier, Asynchronous replication; for any other tier, its commitments appear in the same column. The values are only entered during the test.

Disaster recovery test report

Structure — values are filled in during the test

TriggerTime
Measuredfilled in during the test
Guaranteedno commitment
Measured recovery timeagainst RTO
Measuredfilled in during the test
Guaranteed2 h
Actual data stateagainst RPO
Measuredfilled in during the test
Guaranteed15 min

Technical checkpoints · defined by you

  • Login
  • A read and a write operation
  • A report or an API request

Deviations · one row per deviation

Deviation
filled in during the test
Action
filled in during the test
Deadline
filled in during the test
Responsibility
filled in during the test
Report within five working days · retest of a failed test within 30 days
A single open rack with a switch and four compute nodes, separated from a row of populated racks by an empty aisle.
The test runs in an isolated target network: same addresses, same names, no route to production. What starts up there is the state that is already in the target region anyway.

When a test is passed

All three criteria must apply. Two out of three is not a partial success, but a finding — and triggers the same treatment as a complete failure.

  • Time met: The measured recovery time is at or below the committed RTO of the booked tier.
  • Data state met: The gap between the last committed write operation and the trigger time is within the committed RPO.
  • Functionally passed: Every previously defined functional test point is passed. A system that has started but does not respond functionally is considered not recovered.

If it is not passed

A test without consequences is not a test. What follows a failure is therefore determined in advance — including the uncomfortable consequence for the commitment.

Repetition within 30 days
A failed test is repeated within 30 calendar days. It does not count as one of the contractually scheduled tests for the year — otherwise a failure would use up the testing budget intended to fix it.
Blameless root cause analysis
The system is investigated, not the person at the button. The report names the triggering condition, the chain up to the impact and the point where a safeguard was missing.
Commitment suspended, not tacitly kept
Until the repetition is passed, the time commitment of the tier is considered suspended. We do not carry forward a recovery time that was not achieved last time.

What must be present on your side

A recovery fails just as reliably due to a missing time source as it does due to missing capacity. These three points lie outside of what an operator can guarantee — they are nevertheless part of the commitment because they determine its outcome.

A runbook that works without its author

The order of the systems, the dependencies between them and the functional test points are documented in writing and cross-checked during every test. A runbook that only its author can execute is not a runbook.

Named dependencies outside replication

Directory service, name resolution, time source, licence server, payment provider: what lies outside the protected environment does not start up with it. Every such dependency needs its own answer before it becomes apparent in the test.

Access routes that survive the failure

Access data, second factors and emergency contacts are not located exclusively in the environment that is to be recovered. This sounds obvious and is the most common finding of the first test.

Three things this page explicitly does not cover

A recovery tier answers exactly one question: how does an environment come back if its location fails. It does not answer three related questions — and anyone who overlooks this buys the wrong commitment.

Availability during operations

The committed availability, its measurement method and the service credit scale are in the Service Level Agreement. They measure the ongoing operations of a platform. A recovery case begins where this measurement ends: with the loss of the location where the measurement took place. A level on this page therefore does not replace an availability class — and an availability class does not replace a recovery level.

Restriction: Service credits according to the SLA scale arise from availability falling short, not from an exceeded recovery time. The testing procedure applies to the time commitments on this page, not the service credit scale.

Protection against your own mistakes

Replication transfers every write operation, even the wrong ones. A deleted table, an encrypted file share or a faulty procedure will be exactly the same at the second location after the transfer. Only retention helps against this: a previous state that is not overwritten. Snapshot retention depends on the datastore class and lasts up to 90 days.

Datastore NVMe Performance
14 days
Datastore NVMe Standard
14 days
Datastore Capacity
30 days

Restriction: Even the tightest level, Asynchronous replication, propagates an error with the next run — after 15 minutes at the latest. No level replaces the backup, each complements it.

Capacity at the destination

A recovery time assumes that something starts up at the destination. The other two levels solve this differently — and both answers have a condition that is not included in the time specification. If you need a round-the-clock time commitment, you book the capacity reservation; it is not an accessory, but the reason why the number applies.

Restriction: The restart uses free capacity in the target region. Without booked capacity reservation, the RTO commitment only applies Mon–Fri 08:00–18:00; outside this time, there is no guaranteed restart time.

Restriction: A single host runs in the target region with around 25% of the productive capacity. Full throughput is only available after adding more hosts — lead time up to 90 minutes.

A pulled-out storage chassis with dozens of vertical drives in a grid; one drive is lifted halfway out by its handle.
Replication keeps a second location, retention an earlier point in time. The difference is measurable: Asynchronous replication carries a wrong write operation to the second location after 15 minutes, the snapshot retention of ENTRONYX CLOUD keeps the previous state for up to 90 days.

What you order as protected is protected. Volumes that are not in the protected capacity are not there after a location loss — even if they were on the same datastore. The smallest sensible protected capacity is therefore not zero, but the scope that a recovery actually needs — and that is never below the minimum purchase of the operational datastore, from 1 TB.

What is usually asked before choosing a tier

Ten questions that regularly come up before an order. The answers state the same catalogue values as the sections above.

Your question is not included? In the downtime simulator, each tier shows times, the monthly amount and the condition that applies. We answer everything else via the contact form.

What is disaster recovery for the Private Cloud, and what does it cost per month?

Disaster recovery is the second copy of your environment at another location in Germany, with guaranteed recovery point objective (RPO) and guaranteed recovery time objective (RTO) per tier. 3 tiers range from “Secured recovery” to “Asynchronous replication”; the price consists of a base fee per protected environment and a rate per protected gigabyte and month.

Base fee from, per protected environment and month, net€149.00$172.84

Simulate downtime

How quickly does support respond if a host fails?

An outage (P1) receives an initial response in 30 minutes, around the clock, in the Platform operations, which is included in every managed host; from the “Platform and guest operations” level it is 15 minutes. Initial response means: a human has accepted the report, classified it and reported back the processing status — we do not guarantee a resolution time. Reports are made via the ticket in the account; a change without an outage requires the lead time of the operations level, in the Platform operations 48 hours.

Failover and failback process

What is the term, and how do I cancel?

Without a term agreement, the contract runs for one month and renews for another; terms of 12 or 24 months are paid in advance and you receive a 5% or 8% term discount respectively. You can cancel monthly contracts with one day's notice to the end of the term, contracts for 12 or 24 months with 30 calendar days' notice — otherwise they renew for twelve months. After the contract ends, your data remains accessible for 30 calendar days; after that, it is irretrievably deleted.

What is the difference between RPO and RTO?

The Recovery Point Objective (RPO) states how much work is lost in a disaster; the Recovery Time Objective (RTO) states how long it takes until your application provides its first functional response. Both are guaranteed separately per tier: the RPO from 15 minutes to 24 hours, the RTO from 2 hours to 8 hours. Each of the two figures only applies under a specific condition, which is stated for each tier.

The tiers on the timeline

Which tier do I need?

The tier whose data loss your application can tolerate: Secured recovery loses up to 24 hours of work in an emergency, Pilot Light up to 4 hours of work and Asynchronous replication up to 15 minutes of work. Secured recovery only meets its time commitment without capacity reservation on weekdays during the day window.

Simulate downtime

How is the price calculated?

From a fixed base fee per protected environment and a rate per protected gigabyte and month; both are shown separately. The base fee pays for orchestration, runbook, the provisioned target environment and the annual tests, the rate pays for the second copy of the data. Recovery is added to hosts, licences, datastore and operations and does not replace any of these items.

Base fee from, per protected environment and month, net€149.00$172.84

Both components per tier

Where is it replicated to?

In Germany — from dus1 to a second location that meets the target rule of the respective tier; each tier requires a distance of at least 150 km.

Permitted targets per tier

Who triggers the failover in a disaster?

A named person in your organisation — the failover is not decided by us, in any tier. After a failover, the environment runs at a single location until failback, and during this time no tier commitment applies.

Failover and failback process

What is a recovery test, and how often does it take place?

An announced recovery from the latest replica into an isolated target network, depending on the tier 1 to 4 times a year; production continues unchanged. The test is only passed if the recovery time, data state and your functional checkpoints are met, and you receive a report with the measured values afterwards. If it fails, it is repeated, and until then the time guarantee of the tier is considered suspended.

Procedure and report of a test

Does a recovery tier replace data backup?

No, no tier replaces the backup — each complements it. A replication transfers every write operation, even the wrong one; against an accidentally deleted table, only a retained previous state helps. Snapshot retention depends on the datastore class and goes up to 90 days.

What this page does not cover

Base from · per environment and month, net€149.00$172.84

Simulate downtime

First check the condition, then order the number

In the configurator, host class, datastore, recovery level and operations level are side by side, and the total is calculated using the same rates as this page: base fee per protected environment plus rate per protected gigabyte. If you want to know in advance which level suits your application, do not start with the price, but with the question of how much work an outage is allowed to cost.

Tiers
3
RPO from
15 min
RTO from
120 min
Tests per year
1 – 4