Architecture, distribution and integration
Backup, restore and continuity design
Recovery structure: what is backed up, where copies live, and the restore path for each failure mode.
ddn@1New DDN source
Why use it?
Backups nobody has restored are a hope; the restore path is the design.
When it helps
Continuity planning and disaster-recovery reviews.
How to read it
- Read backwards from each failure mode to the copy that answers it.
- RPO/RTO notes attach to the restore path, not the backup schedule.
What you need
- The protected systems
- Copy locations and schedules
- Restore steps per failure mode
Things to check
- Do not document a backup without its restore test.
- Do not let one site hold both primary and only copy.
Scope of this diagram
Design documentation; no actual recovery is executed or timed here.
Work with the converted example
- Open the viewer and select
diagram. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.