SLA, Availability, MTTR and Fault Domains

Learning outcomes

• Convert an SLA percentage to a downtime budget
• Explain the roles of MTBF and MTTR
• Draw a useful fault-domain boundary

INHERENT AVAILABILITY

A = MTBF ÷ (MTBF + MTTR)

Operational availability may also include maintenance, logistics and administrative delay.

An SLA is a measured commitment

A service-level agreement defines the service, measurement window, exclusions and consequence of missing the target. “99.9%” alone is incomplete: the endpoint, clock, calculation, maintenance rules and remedy all matter.

Availability percentages become small downtime budgets at high targets. Operators therefore need monitoring that measures the same service the customer experiences, not only green infrastructure lights.

Recovery time is an engineering variable

MTBF summarizes the average operating interval between repairable failures. MTTR usually describes mean time to repair or restore, but teams must define which. Faster detection, clear runbooks, accessible spares, practiced escalation and reversible change can reduce recovery time.

A high-reliability component can still produce a long outage if diagnosis or replacement is slow. Conversely, a component that fails more often may have limited service impact when it is isolated and quickly restored.

Fault domains contain blast radius

A fault domain is the set of resources expected to fail together: a rack, power path, network zone, cooling loop, software cluster or site. Redundancy should cross the boundary of the failure it is meant to survive.

Document dependencies and test assumptions. Two services in different racks may still share a switch, PDU, control plane or change process. Common-mode and human failures frequently ignore labels drawn on a diagram.

How it appears in Data Center Fan

Contracts declare compute, memory, bandwidth and SLA requirements. Incidents read real facility state, while forced downtime drops service and recovery gradually rebuilds uptime instead of snapping back to perfect.

Common misconception

“99.9% means only one short outage is allowed.” The budget is cumulative within the stated window unless the agreement says otherwise.

Knowledge check

Which change most directly improves availability when MTBF stays constant?

• Reduce MTTR
• Increase rack height
• Add unused IP addresses

With MTBF fixed, lowering restoration time reduces the fraction of time the service is unavailable.

Authoritative sources

• NIST SP 800-34 Rev. 1 — Contingency Planning Guide
• Uptime Institute — Data Center Tier Classification