# IBM i Restore Time and RTO Calculator

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

## Short answer

Add up restore, journal apply and verification time for an IBM i recovery and compare it with your recovery time objective.

## Category

oracle

## Erp

Oracle JD Edwards World

## Audience

- IBM i administrator
- IT manager
- CIO

## Tool

**Kind:** calculator

**Inputs:**

#### Data to restore

**Key:** data

**Type:** number

**Default:** 1500

**Min:** 1

**Step:** 50

**Unit:** GB

#### Sustained restore throughput

**Key:** rate

**Type:** number

**Default:** 300

**Min:** 10

**Step:** 10

**Unit:** GB/hour

**Help:** Measure from a real restore test. Tape drive speed, number of drives and parallel restore jobs all change this.

#### Setup time before data restore

**Key:** setup

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** hours

**Help:** Hardware access, install of Licensed Internal Code and IBM i, then user profiles and configuration.

#### Journal changes to apply

**Key:** journal

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** GB

**Help:** Receivers since the last full save, if you recover to a point near the failure.

#### Journal apply throughput

**Key:** apply_rate

**Type:** number

**Default:** 60

**Min:** 1

**Step:** 5

**Unit:** GB/hour

#### Verification and application checks

**Key:** verify

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### Recovery time objective

**Key:** rto

**Type:** number

**Default:** 24

**Min:** 1

**Step:** 1

**Unit:** hours

**Outputs:**

#### Data restore time

**Key:** restore_h

**Expr:** data / rate

**Format:** hours

#### Journal apply time

**Key:** apply_h

**Expr:** journal / apply_rate

**Format:** hours

#### Total recovery time

**Key:** total_h

**Expr:** setup + restore_h + apply_h + verify

**Format:** hours

**Primary:** true

#### Margin against RTO (negative means missed)

**Key:** gap

**Expr:** rto - total_h

**Format:** hours

**Primary:** true

#### Restore throughput needed to meet RTO

**Key:** need_rate

**Expr:** if(gt(rto - setup - apply_h - verify, 0), data / (rto - setup - apply_h - verify), 0)

**Format:** number

**Description:** Gigabytes per hour. Zero means the fixed steps alone exceed the RTO.

**Chart:**

#### Total recovery hours vs restore throughput

**Type:** line

**X:** rate

**From:** 100

**To:** 1000

**Steps:** 19

**Series:**

- total_h

**Disclaimer:** Estimates only. Run a full restore test to a spare partition or recovery site before relying on any figure.

## Content

**Intro:** Most AS/400 shops can tell you the backup schedule but not how long a full recovery would take. This calculator turns your restore speed and data size into a recovery time you can compare with the business requirement.

**Sections:**

#### How to use it

**Body:** Enter the data volume you would need to bring back for the business to run, not the whole disk. Use a restore throughput measured in a test, because tape specifications overstate real speed when files are small or when many objects are restored sequentially. Add setup time for hardware, installing the operating system and restoring user profiles and security.

#### The method

**Body:** Total recovery time is setup plus data divided by restore rate, plus journal volume divided by apply rate, plus verification time. The tool also solves backwards: given your recovery time objective, the throughput you would need is data divided by the time left after the fixed steps. The chart shows how total time falls as throughput rises, with sharply diminishing returns above a point.

**Bullets:**

- Restoring libraries in parallel jobs can raise throughput if you have enough drives or a virtual tape library
- Large numbers of small objects restore slower than a few large ones
- Journal apply is often slower than people expect

#### How to read it

**Body:** If you miss the objective, look first at the setup and verification terms, which are often padding for no good reason, then at throughput. If the needed throughput is above anything your hardware has ever done, the answer is a different architecture, such as replication to a second system, not faster tape. A negative margin should be taken to management as a gap with a price.

#### Common mistakes

**Body:** Assuming the vendor's rated speed is what you will get, forgetting the time to find and mount media, leaving out the time to restore security data and authorities, and never testing. Also confirm that offsite or cloud backups can be retrieved at the rate you assume; a slow network link can dominate the whole calculation.

**Cta:** If you want a recovery test plan written for your IBM i environment, Netray can help you structure it and review the results.

**Faq:**

#### What is the difference between RTO and RPO?

**Answer:** RTO is how long the business can be without the system. RPO is how much recent data it can afford to lose. This calculator focuses on RTO, with the journal step standing in for how close to the failure you recover.

#### Is this only for a full system loss?

**Answer:** It models a full recovery. For a library or file restore, use only the relevant data size and set setup to zero.

#### Does it apply to cloud-hosted IBM i?

**Answer:** Yes, but use the restore throughput that your provider's backup service achieves and add any time to request restores. Ask for their tested figures.

#### How often should I test?

**Answer:** At least once a year and after major changes in data volume, hardware or backup software. An untested restore time is a guess.

## Search terms

ibm i restore time, as400 recovery time objective, as400 disaster recovery calculator, savsys restore duration, ibm i rto rpo, jd edwards world disaster recovery, tape restore speed calculator

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