返回提示词目录第 1158 页

制定系统备份与灾难恢复方案

按系统依赖和恢复目标制定备份策略、分场景恢复顺序及演练清单,标明缺失信息与风险。

完整提示词

<context>
Disaster-recovery plans fail on the things nobody listed: backups that were never restored, replicas that faithfully copied the corruption, the secrets manager or the backup credentials living in the region that went down, a DNS change only one person knows how to make. A useful plan is specific to the system, measured in minutes and data lost, and proven by drills.
</context>

<task>
Write a backup and disaster-recovery plan for:
{{system}}
{{#rpo}}Recovery point objective (maximum data loss): {{rpo}}
{{/rpo}}{{#rto}}Recovery time objective (maximum time to restore): {{rto}}
{{/rto}}

1. If a recovery point objective or a recovery time objective is not stated above, propose per-tier targets for whichever is missing with reasoning and mark them "proposed, needs business sign-off". Do not present them as decided.
2. Inventory every component and data store. Assign each a tier, and list what it depends on to start: identity, secrets, DNS, certificates, container registry, CI/CD, third-party APIs.
3. Cover these scenarios separately, because each needs a different answer: accidental deletion, logical corruption (replication copies it, so point-in-time recovery is required), loss of a zone, loss of a region, compromised cloud account or ransomware, and a critical vendor outage.
4. For each data store, specify the backup method, frequency (it must meet the RPO), retention, encryption and where the key lives, and isolation: a separate account or immutable storage so an attacker with production access cannot delete backups.
5. Choose a recovery strategy per tier (backup and restore, pilot light, warm standby or active-active) and justify it against the RTO and cost.
6. Write the recovery order from the dependency graph: what must be up before what, with an estimated time per step and a total compared against the RTO.
7. Define restore drills: what is restored, how often, success criteria (measured RPO and RTO), and who signs off.
</task>

<constraints>
- Replication and high availability are not backups. Do not count them toward recovery from corruption or deletion.
- A backup is only counted as working once a restore of it has been tested. Mark untested backups as risks.
- Use the details given. Where a fact is missing (sizes, regions, owners), write a clearly marked placeholder and list it under Open risks rather than inventing it.
{{> output/uncertainty}}
</constraints>

<output_format>
## Summary
The targets (stated or proposed), the strategy per tier, and the three biggest gaps today.
## Inventory
A table: component, tier, data store (yes/no), depends on, current backup, gap.
## Scenarios
One short subsection per scenario: detection, decision owner, recovery path, expected data loss and downtime.
## Backup policy
A table: data store, method, frequency, retention, isolation, encryption key location, last tested restore.
## Recovery order
Numbered steps with estimated durations and a total against the RTO.
## Drills
A table: drill, frequency, success criteria, owner.
## Owner checklists
One checklist per role (for example incident lead, database owner, platform owner).
## Open risks
Bullets: missing information and unproven assumptions.
</output_format>

可替换内容

  • {{system}}
  • {{#rpo}}
  • {{rpo}}
  • {{/rpo}}
  • {{#rto}}
  • {{rto}}
  • {{/rto}}
  • {{> output/uncertainty}}

分类与标签

编程开发、灾难恢复、备份策略、恢复目标、恢复演练、基础设施运维

前往 AI 图片创作