RTO/RPO Tier Classifier

Classify RTO and RPO against caller-defined application-tier limits.

Description

RTO limits recovery duration while RPO limits tolerated data-loss time.

RTO limits recovery duration while RPO limits tolerated data-loss time. Both objectives must satisfy the selected tier.^[1]

Classify RTO and RPO against caller-defined application-tier limits.

When to use RTO/RPO Tier Classifier

Use this tool to classify RTO and RPO against caller-defined application-tier limits.

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.

How to use RTO/RPO Tier Classifier and understand its results

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
Enter rtoHours, rpoHours, tierOneMaxRtoHours, tierOneMaxRpoHours, tierTwoMaxRtoHours, tierTwoMaxRpoHours using the field table and calculation rules, then run the tool.
Read tier, meetsTierOne, meetsTierTwo. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
rtoHours	Recovery time objective (h)	number; minimum: 0	Required
rpoHours	Recovery point objective (h)	number; minimum: 0	Required
tierOneMaxRtoHours	Tier-one maximum RTO (h)	number; minimum: 0	Required
tierOneMaxRpoHours	Tier-one maximum RPO (h)	number; minimum: 0	Required
tierTwoMaxRtoHours	Tier-two maximum RTO (h)	number; minimum: 0	Required
tierTwoMaxRpoHours	Tier-two maximum RPO (h)	number; minimum: 0	Required

Enter nonnegative hours/limits with tier-one limits no looser than tier-two. Return tier and both inclusive gates.

tier-one when both≤tier1; else tier-two when both≤tier2; else tier-three

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
tier	Application tier	string; one of "tier-one", "tier-two", "tier-three"
meetsTierOne	Meets tier-one limits	boolean
meetsTierTwo	Meets tier-two limits	boolean

json

{
  "input": {
    "rtoHours": 2,
    "rpoHours": 1,
    "tierOneMaxRtoHours": 1,
    "tierOneMaxRpoHours": 0.5,
    "tierTwoMaxRtoHours": 4,
    "tierTwoMaxRpoHours": 2
  },
  "output": {
    "tier": "tier-two",
    "meetsTierOne": false,
    "meetsTierTwo": true
  }
}

Limitations and assumptions

No recovery test, achieved downtime or data loss is verified.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use Failover Evidence Coverage: Audit disaster-recovery failover evidence. For a complementary task, use Continuous-Close Freshness: Measure continuous-close data freshness and pipeline-check status.

References

RTO/RPO Tier Classifier — tool.io

Similar or alternative tools

Failover Evidence Coverage
Audit disaster-recovery failover evidence.
Continuous-Close Freshness
Measure continuous-close data freshness and pipeline-check status.