36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
---
|
||
title: "RTO (Recovery Time Objective)"
|
||
type: concept
|
||
tags: [灾难恢复, 业务连续性, 指标]
|
||
sources: ["https://launchdarkly.com/blog/rto-vs-rpo/"]
|
||
last_updated: 2025-07-26
|
||
---
|
||
|
||
## Definition
|
||
RTO（Recovery Time Objective，恢复时间目标）是指系统允许的最大停机时间。是从系统下线到恢复上线的最大可接受时间窗口。
|
||
|
||
## Key Characteristics
|
||
- 衡量恢复速度，而非数据丢失
|
||
- 时钟从系统下线时刻开始计时
|
||
- 与业务影响直接相关
|
||
- 需要与 RPO 共同规划，不能只优化其中一个
|
||
|
||
## Tiered RTO Targets (from this source)
|
||
| Tier | Examples | RTO Target |
|
||
|------|----------|------------|
|
||
| Critical | Payment processing, user auth | < 5 minutes |
|
||
| Important | Admin dashboards, reporting | < 1 hour |
|
||
| Nice-to-have | Internal tools, dev environments | < 4 hours |
|
||
|
||
## RDS vs Aurora RTO Comparison
|
||
| Database | RTO (AZ Failure) |
|
||
|----------|-----------------|
|
||
| Aurora | 30 秒 |
|
||
| RDS PostgreSQL | 2 分钟 |
|
||
|
||
## Connections
|
||
- [[RPO (Recovery Point Objective)]] ← 配对指标 → [[RTO (Recovery Time Objective)]]
|
||
- [[灾难恢复]] ← 应用领域 → [[RTO (Recovery Time Objective)]]
|
||
- [[持续交付]] ← 现代上下文 → [[RTO (Recovery Time Objective)]]
|
||
- [[Feature Flag]] ← 降低工具 → [[RTO (Recovery Time Objective)]]
|