Loading content
Disaster recovery defines strategies, processes and technologies to restore IT systems and data after major outages. The goal is to minimize downtime (RTO) and data loss (RPO) through planning, backups, replication and tested recovery procedures. It covers organizational processes, technical measures and regular validation tests.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
It is a planned way to restore critical IT services and data after a major outage.
The approach grew from the operational need to resume essential functions after disasters, hardware failures, or serious configuration mistakes.
Follow the chain: detect the outage, assess damage, access protected resources, restart priorities, and stabilize service. RTO sets time; RPO sets acceptable data loss.
Core idea is a distinct part of this topic and guides its practical use.
Mechanism is a distinct part of this topic and guides its practical use.
Practice context is a distinct part of this topic and guides its practical use.
Use it for critical services and high-impact changes. Redundancy and faster targets cost more, and an untested plan remains an assumption.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.