What it means
Maximum tolerable downtime, often abbreviated MTD, expresses a business limit rather than a technology target. It reflects the point at which accumulated operational, safety, financial, legal, customer, or reputational harm can no longer be accepted.
How it works
The value comes from business impact analysis and should account for changing consequences over time. Recovery time objectives, manual workarounds, restoration sequencing, and supporting-service targets must fit within the overall tolerance. An MTD of eight hours does not mean every technical component may take eight hours to recover.
A customer-ordering process may become unacceptable after eight hours. Identity, network, database, application, payment, and staffing dependencies need coordinated objectives that restore a usable service before that limit.
Practical focus
- Define MTD at the business-process level
- Include peak periods and regulatory or safety deadlines
- Ensure component objectives and workarounds collectively fit within the tolerance
- Test whether plans achieve a usable business outcome, not merely server startup
Common mistakes
- Setting MTD based only on current backup technology
- Confusing MTD with recovery time objective
- Ignoring degraded operations and dependency recovery
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: