{"canonical_url":"https://engineer.company/glossary/recovery-time-objective/","content_markdown":"# Recovery time objective\n\n## What it is\n\nA recovery time objective, abbreviated RTO, is the target elapsed time to restore an agreed\nservice capability following a disruption. It answers how long the organization can plan to do\nwithout that capability before the consequences become unacceptable. An effective objective includes\nthe event that starts the clock and the behavior that proves the service is useful again. Starting\nfrom detection can omit an unnoticed outage. Stopping at a successful process start can omit a\nservice that customers still cannot use.\n\nNIST's contingency planning guide describes the RTO as the maximum time a system resource may\nremain unavailable before there is an unacceptable impact on other system resources, supported\nbusiness processes and the maximum tolerable downtime. The guide places recovery objectives within\nthe business impact analysis. A team can start with the work that needs to resume and reason back to\nthe components it needs. In a chain of services, the database and identity service may each need to\nbe ready well before the application must be usable.\n\nThe recovery point objective, or RPO, answers how far back the team can accept losing updates. A\nservice can be usable in twenty minutes with four hours of changes missing. It can also recover all\nupdates and still take half a day. Both objectives matter. A service level objective for availability\nusually counts service behavior across a period, such as the proportion of good requests in a month.\nAn RTO addresses a defined recovery after a disruption. Several recoveries within their RTO can\nstill consume more of a monthly availability budget than the service owner intended.\n\n## Why it matters\n\nThe target governs investment. A team that can tolerate a morning of downtime may be able to use a\ntested restore into a fresh environment. A team that needs a usable service in minutes may need\ninfrastructure already in place, automated recovery checks and people available to take decisions\nquickly. The elapsed time includes more than moving data. Detecting the problem, reaching a responder,\nmaking a decision, preparing dependencies, verifying the service and switching users over can all\nspend time.\n\nA recovery target also makes the business decision precise. Visitors may tolerate a read-only\ncatalogue for longer than they can tolerate a failed checkout. Staff may be able to use a manual\nprocess for a short time but fall behind as new work arrives. Defining the level of service expected\nat the end of the interval makes those costs visible. Some organizations define one target for\nminimum useful operation and a later milestone for clearing the backlog and restoring every function.\n\nAn objective is a plan, while the result of an exercise is an observation. A successful recovery\non a lightly loaded test system may not demonstrate that a full restore fits the same deadline. A\nuseful result describes the volume of data, dependencies available, who responded and the criteria\nused to decide that customers could return. That lets readers judge what the exercise supports and\nwhat it leaves unknown.\n\n## What it looks like in practice\n\nImagine an order service whose owners set a two-hour recovery objective for accepting and recording\nnew orders. The clock starts when customers can no longer place orders. The exercise may use a test\nharness to mark the interruption, so the team can measure the time spent before detection. The service\nis considered restored when a set of representative orders reaches payment confirmation and appears\nin the records the warehouse uses. A working catalogue alone would leave the recovery clock running.\n\nIn the exercise, detecting the outage takes twelve minutes. Declaring the incident, checking which\ncopy to restore and authorizing the operation take eighteen more. Restoring data takes forty-five\nminutes. The team spends thirty minutes reconnecting dependencies, testing orders and opening the\nroute again. The observed result is 105 minutes, leaving fifteen minutes from the two-hour target.\nThe team separately checks the age of its newest recovered order against the target for data loss.\n\nThis exercise shows how the current procedure performed with those dependencies and that data.\nVariation between attempts helps decide what to improve. If reconnecting dependencies took much\nlonger than expected, it may be worth preparing the configuration in advance. If nobody could\nauthorize the operation during one shift, the team might clarify who is allowed to make that\ndecision. A later exercise can test the change with a realistic amount of data and different\nresponders, using the same start and stop criteria.\n\nEngineer's [backup and restore-test case](/portfolio/backups-that-have-actually-been-restored/) describes\npractical verification of recovery. The company's [published service levels](/service-levels/)\ndiscuss the terms for supported service, which can include coverage and response commitments. The\ntwo-hour objective and timings in the order scenario are hypothetical. A reader needs an agreed\nrecovery objective for their own service and an exercise that observes its actual return.\n\n## Where it goes wrong\n\n**The clock uses a convenient timestamp.** Starting when the operator begins a restore omits the\ntime users already spent waiting. Agree on what counts as a disruption, collect timestamps for\ndetection and action, and report which interval is being measured.\n\n**The system is called recovered when a component starts.** A healthy database or a successful\ndeployment can coexist with failed payments. Test the capability the target is intended to protect\nthrough a representative user journey and its downstream records.\n\n**Every component gets the same target.** A service may wait for a storage restore, an identity\nprovider and a manual decision. Give dependencies enough time within the joint timeline and allow\nfor work that actually has to run in sequence.\n\n**An untested number becomes a promise.** Record the target explicitly and compare it with measured\nresults, including failed or slow exercises. Preserve the conditions of each test. This makes it\npossible to update the plan where needed and prevents a single fast run from standing for all\noutage scenarios.\n\n## Further reading\n\n- [NIST SP 800-34 Rev. 1](https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final) — contingency planning, business impact analysis and the relationship between recovery objectives and tolerable downtime.\n- [AWS guidance on recovery objectives](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_planning_for_recovery_objective_defined_recovery.html) — defining objectives for downtime and data loss.\n- [Microsoft Azure on business continuity and recovery](https://learn.microsoft.com/en-us/azure/reliability/concept-business-continuity-high-availability-disaster-recovery) — recovery objectives and the distinctions among availability and recovery capabilities.\n\n\u003chttps://engineer.company/glossary/recovery-time-objective/\u003e\n","date_modified":"2026-11-19T19:18:49Z","description":"How to set a recovery time objective, define what counts as restored and check the target in a realistic recovery exercise.","formats":{"gemtext":"https://engineer.company/glossary/recovery-time-objective/index.gmi","gopher":"https://engineer.company/glossary/recovery-time-objective/gophermap","html":"https://engineer.company/glossary/recovery-time-objective/","json":"https://engineer.company/glossary/recovery-time-objective/index.json","markdown":"https://engineer.company/glossary/recovery-time-objective/index.md","pdf":"https://engineer.company/glossary/recovery-time-objective/index.pdf"},"kind":"page","language":"en","title":"What is a recovery time objective?","url":"https://engineer.company/glossary/recovery-time-objective/","version":1}