168:
47:
for example. However, the failed device involved in this redundant configuration still needs to be returned to service and hence the device itself has a non-zero MTTR even if the system as a whole (through redundancy) has an MTTR of zero. But, as long as service is maintained, this is a minor issue.
38:
The MTTR would usually be part of a maintenance contract, where the user would pay more for a system MTTR of which was 24 hours, than for one of, say, 7 days. This does not mean the supplier is guaranteeing to have the system up and running again within 24 hours (or 7 days) of being notified of the
42:
Note that some suppliers will interpret MTTR to mean 'mean time to respond' and others will take it to mean 'mean time to replace/repair/recover/resolve'. The former indicates that the supplier will acknowledge a problem and initiate mitigation within a certain timeframe. Some systems may have an
34:
time that a device will take to recover from any failure. Examples of such devices range from self-resetting fuses (where the MTTR would be very short, probably seconds), to whole systems which have to be repaired or replaced.
39:
failure. It does mean the average repair time will tend towards 24 hours (or 7 days). A more useful maintenance contract measure is the maximum time to recovery which can be easily measured and the supplier held accountably.
205:
44:
92:
43:
MTTR of zero, which means that they have redundant components which can take over the instant the primary one fails, see
237:
105:
198:
227:
62:
138:
242:
72:
191:
179:
113:
17:
8:
57:
232:
31:
175:
67:
221:
167:
93:"Also refer to "Mean Time To Repair" or "Mean Time To Restore""
139:"MTBF, MTTR, MTTF, MTTA: Understanding incident metrics"
219:
199:
206:
192:
220:
136:
162:
174:This business-related article is a
13:
14:
254:
166:
130:
99:
85:
1:
78:
178:. You can help Knowledge by
106:INTEL call for Mean-Time-to-
7:
51:
10:
259:
161:
63:Mean time between failures
15:
238:Reliability engineering
73:Service-level agreement
24:Mean time to recovery
18:MTTR (disambiguation)
16:For other uses, see
58:Mean time to repair
228:Disaster recovery
187:
186:
250:
208:
201:
194:
170:
163:
153:
152:
150:
149:
134:
128:
127:
125:
123:
118:
103:
97:
96:
89:
258:
257:
253:
252:
251:
249:
248:
247:
218:
217:
215:
213:
212:
159:
157:
156:
147:
145:
135:
131:
121:
119:
116:
112:
110:on page 4 left.
104:
100:
91:
90:
86:
81:
54:
21:
12:
11:
5:
256:
246:
245:
243:Business stubs
240:
235:
230:
211:
210:
203:
196:
188:
185:
184:
171:
155:
154:
129:
98:
83:
82:
80:
77:
76:
75:
70:
68:Mean down time
65:
60:
53:
50:
9:
6:
4:
3:
2:
255:
244:
241:
239:
236:
234:
231:
229:
226:
225:
223:
216:
209:
204:
202:
197:
195:
190:
189:
183:
181:
177:
172:
169:
165:
164:
160:
144:
140:
133:
115:
111:
109:
102:
94:
88:
84:
74:
71:
69:
66:
64:
61:
59:
56:
55:
49:
46:
40:
36:
33:
29:
25:
19:
214:
180:expanding it
173:
158:
146:. Retrieved
142:
132:
120:. Retrieved
107:
101:
87:
41:
37:
27:
23:
22:
137:Atlassian.
222:Categories
148:2023-09-26
79:References
143:Atlassian
114:"Unknown"
30:) is the
52:See also
233:Failure
32:average
122:May 7,
108:Repair
117:(PDF)
176:stub
124:2020
45:RAID
28:MTTR
224::
141:.
207:e
200:t
193:v
182:.
151:.
126:.
95:.
26:(
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
