Maximum Tolerable Downtime (MTD)

Maximum Tolerable Downtime is the hard deadline. It is the total time a business process can be unavailable before the organisation suffers damage it cannot absorb: lost customers, regulatory penalties, or an existential hit to revenue. MTD is a business judgement set through the business impact analysis, and it frames every recovery decision downstream.

Because it is the outer boundary, the other time metrics live inside it: RTO to restore the system plus WRT to validate data and resume operations must together be less than or equal to the MTD. A short MTD forces investment in faster recovery, hot sites, and replication; a generous MTD permits cheaper, slower strategies. Some sources use Maximum Acceptable Outage as a synonym, and the whole timeline is worked in the recovery metrics guide.

Exam relevance: MTD is the constraint questions test against. Expect to be given RTO and WRT and asked whether a strategy fits, or to be told an MTD and asked what recovery capability it implies. Remember it is set by the business, not IT, and that it bounds time only, while RPO bounds data loss on a separate axis.