Skip to content

Commit 371e2ca

Browse files
committed
Updates
1 parent cd3eb38 commit 371e2ca

4 files changed

Lines changed: 86 additions & 3 deletions

File tree

articles/reliability/concept-business-continuity-high-availability-disaster-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ Due to the rarity and severity of disaster events, DR planning brings different
270270

271271
- **Recovery Time Objective (RTO)** is the maximum duration of acceptable downtime in the event of a disaster, where "downtime" is defined by your specification. RTO is also measured in units of time, like "eight hours of downtime."
272272

273-
:::image type="content" source="media/disaster-recovery-rpo-rto.png" alt-text="Screenshot of RTO and RPO durations in hours." border="false":::
273+
:::image type="content" source="media/concept-business-continuity-high-availability-disaster-recovery/disaster-recovery-rpo-rto.svg" alt-text="Screenshot of RTO and RPO durations in hours." border="false":::
274274

275275
Each component or flow in the workload might have individual RPO and RTO values. Examine disaster-scenario risks and potential recovery strategies when deciding on the requirements. The process of specifying an RPO and RTO effectively creates DR requirements for your workload as a result of your unique business concerns (costs, impact, data loss, etc.).
276276

Lines changed: 83 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)