Cloud
RPO is the amount of data, measured in time, that a recovery design accepts losing. RTO is the time accepted to restore a named service. They are planning terms, not performance claims. Novatelia does not publish either number. A figure exists only in a written backup or recovery service, after the systems and the copy schedule are known.
Revised 2026-10-10. Published by Novatelia. No individual author is named, because no personal credential is claimed for this explanation.
Key points
- The two numbers answer different questions.
- A short RPO needs a frequent copy. A short RTO needs a tested restore path.
- A web page is the wrong place for either commitment.
Definition
Recovery point objective looks backward at data loss. Recovery time objective looks forward at downtime. A design can be strict on one and loose on the other.
How it works
The customer names the service and the loss they can accept. The copy schedule is then checked against that point objective. The restore steps are timed in a test against the time objective. Until that test exists, neither number is known.
Architecture
- A named service, not “the company”.
- A copy schedule compared with the point objective.
- A tested restore compared with the time objective.
Use cases
- A tender asks for RPO and RTO before anyone has listed the systems.
- A backup job runs nightly and someone assumes that means a one-hour loss.
- A restore has never been timed and a four-hour claim is being copied from another project.
Comparison
- RPO
- How far back the last usable copy may be.
- RTO
- How long the named service may stay unavailable.
Selection guidance
- Refuse a number that is not tied to a system and a test.
- Use the backup solution to scope the copies.
- Keep hardware-maintenance response, such as a four-hour part, off this definition. That agreement is a different page.
Questions
What RPO and RTO does Novatelia offer?
None are published. The backup and disaster-recovery solution says a figure exists only in a written service. This article defines the words so a tender does not treat them as a catalog specification.
Is a four-hour maintenance response an RTO?
No. A hardware maintenance window is on the maintenance agreement. RTO is about restoring a named service, which may need data, not only a replaced part.
Related
More in Cloud
This page defines a term so a project can be scoped. It is not a certification, a test result, or a price. Partnerships are stated only on the partners page. The published address and telephone are the company contact, not a service-level commitment.
Describe the requirement
An RFQ saves a browser draft. It does not publish a price or issue a quotation reference.