42 lines
1.9 KiB
Markdown
42 lines
1.9 KiB
Markdown
---
|
||
title: "Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance"
|
||
type: source
|
||
tags: [OpenText, DR, Recovery, BCP, SRE]
|
||
date: 2026-04-14
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Cloud & DevOps/Public-Cloud-Learning-Sessions/10_OpenText-Series/public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2.md]]
|
||
|
||
## Summary
|
||
- 核心主题：灾难恢复（DR）向恢复保障（Recovery Assurance）的演进
|
||
- 问题域：企业级 DR 策略改进与 SRE 实践
|
||
- 方法/机制：通过设计、软件、构建、环境四个维度构建恢复保障能力
|
||
- 结论/价值：从被动响应式测试转向主动式恢复保障架构
|
||
|
||
## Key Claims
|
||
- DR 需要从被动响应转向Recovery Assurance的主动式架构
|
||
- RTO（恢复时间目标）和RPO（恢复点目标）是DR策略的核心指标
|
||
- 恢复保障应是设计原则，而非事后补救
|
||
- SRE和可观测性工程是提升恢复能力的关键技术
|
||
|
||
## Key Quotes
|
||
> "CrowdStrike was not us, but we have had some disruptions." — Jim Rose, 提及基础设施安全事件对DR策略的影响
|
||
|
||
> "Every person who is a SME on some part of this has to be involved in developing a plan." — Jim Rose, 描述DR测试的复杂性
|
||
|
||
## Key Concepts
|
||
- [[Recovery Assurance]]：恢复保障，从设计层面确保系统具备恢复能力
|
||
- [[SRE]]：站点可靠性工程，将软件工程方法应用于运维
|
||
- [[Observability Engineering]]：可观测性工程，通过持续监控理解系统健康状态
|
||
|
||
## Key Entities
|
||
- [[OpenText]]：企业解决方案公司，主办本次学习活动
|
||
- [[Jim Rose]]：演讲者，DR/Recovery Assurance专家
|
||
- [[CrowdStrike]]：安全公司，其安全事件推动了行业对DR的重视
|
||
|
||
## Connections
|
||
- [[DR]] ← evolves_to ← [[Recovery Assurance]]
|
||
- [[RTO]] ← core_metric ← [[Recovery Assurance]]
|
||
- [[RPO]] ← core_metric ← [[Recovery Assurance]]
|
||
- [[SRE]] ← enables ← [[Recovery Assurance]] |