# Ransomware Recovery Time Objective Calculator

> Source: https://netray.co/tools/ransomware-recovery-time-objective-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate realistic hours to restore a plant after ransomware from data volume, restore speed, server rebuilds and validation.

## Category

erp-operations

## Audience

- IT security lead
- IT director
- Backup administrator
- CISO

## Tool

**Kind:** calculator

**Inputs:**

#### Data to restore

**Key:** data_tb

**Type:** number

**Default:** 20

**Min:** 0

**Step:** 1

**Unit:** TB

**Help:** Total size of the systems restored from backup.

#### Effective restore throughput

**Key:** restore_gbps

**Type:** number

**Default:** 4

**Min:** 0.1

**Step:** 0.5

**Unit:** Gbps

**Help:** Measured in a restore test, not link speed.

#### Servers to rebuild or reimage

**Key:** servers

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 1

**Help:** Include domain controllers, ERP, MES and file servers.

#### Hours per server rebuild

**Key:** rebuild_hours

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### Parallel recovery teams

**Key:** teams

**Type:** slider

**Default:** 3

**Min:** 1

**Max:** 10

**Step:** 1

#### Decision and containment time

**Key:** decision_hours

**Type:** number

**Default:** 12

**Min:** 0

**Step:** 1

**Unit:** hours

**Help:** Time to confirm scope, isolate and get approval to restore.

#### Application validation time

**Key:** validation_hours

**Type:** number

**Default:** 16

**Min:** 0

**Step:** 1

**Unit:** hours

**Outputs:**

#### Data restore time

**Key:** restore_h

**Expr:** data_tb * 8000 / (restore_gbps * 3600)

**Format:** hours

**Description:** 1 TB is about 8,000 gigabits.

#### Server rebuild time

**Key:** rebuild_h

**Expr:** servers * rebuild_hours / teams

**Format:** hours

#### Estimated total recovery time

**Key:** total_h

**Expr:** decision_hours + rebuild_h + restore_h + validation_hours

**Format:** hours

**Primary:** true

**Description:** Assumes rebuild and restore run in sequence.

#### Total in days

**Key:** total_d

**Expr:** total_h / 24

**Format:** days

**Primary:** true

#### Share of time spent restoring data

**Key:** restore_share

**Expr:** restore_h / max(total_h, 1) * 100

**Format:** percent

**Chart:**

#### Total recovery hours vs restore throughput

**Type:** line

**X:** restore_gbps

**From:** 1

**To:** 20

**Steps:** 20

**Series:**

- total_h

**Disclaimer:** A planning estimate with simplifying assumptions. Real recoveries hit surprises such as missing credentials, certificates, and dependencies. Validate with an actual restore test.

## Content

**Intro:** How long would it really take to bring the plant back after ransomware? This calculator adds decision time, server rebuilds, data restore and validation into a total, so your recovery objective is based on arithmetic rather than hope.

**Sections:**

#### How to use the calculator

**Body:** Enter the data you would restore from backup, the throughput measured in a real restore test, how many servers need rebuilding and how many people can work in parallel. Add the time it takes to decide, contain and begin, plus validation time for applications. The result shows hours and days, and the chart shows how throughput changes the total.

**Bullets:**

- Use measured throughput, not link speed
- Count identity and network servers first
- Be honest about decision time
- Add validation time for ERP and MES

#### The method

**Body:** Restore time is data in gigabits divided by throughput in gigabits per second. Rebuild time is servers times hours each, divided by parallel teams. Total time is decision, rebuild, restore and validation added in sequence. This is conservative because some work can overlap, but dependencies such as directory services before applications often force sequence.

#### Reading the result

**Body:** If the total exceeds the tolerance of production and customers, the biggest lever is usually not backup speed. Look at the share of time spent restoring data. If it is small, improve decision readiness, automate server builds or tier restore by priority. If it is large, improve throughput or restore critical systems first.

#### Common mistakes

**Body:** Using the backup vendor's maximum speed, forgetting that the attacker may have encrypted the backup tier, ignoring staff fatigue, and counting only the ERP database instead of the identity and network layers that must return before it.

**Cta:** If you want a recovery plan with systems ordered by dependency, we can help build one. The calculator is free and complete.

**Faq:**

#### Why is real recovery slower than the estimate?

**Answer:** Surprises add time: missing credentials, expired certificates, undocumented dependencies, damaged backups, and people working long hours. Treat the estimate as a floor and test to see how far above it you land.

#### What throughput should I enter?

**Answer:** The rate measured in a restore test of a comparable system to the same destination, including decryption, dedupe rehydration and network limits. Vendor maximums are rarely achieved in an incident.

#### Can restores run in parallel?

**Answer:** Often yes for independent systems, which would shorten the total. Directory services and networking usually must come first. Use the sequential total as a cautious figure and adjust once you know your dependencies.

#### How do I shorten recovery?

**Answer:** Restore in priority order, keep immutable or offline copies near the recovery site, pre-build gold images, rehearse the process, and agree decision authority in advance. Faster storage only helps if restore is the bottleneck.

## Search terms

ransomware recovery time calculator, RTO calculator backup restore, how long to restore from backup, disaster recovery time estimate, restore time calculator TB, ransomware recovery estimate, backup restore throughput calculator, recovery time objective calculator

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json