IT Continuity Fundamentals
Availability, continuity, recovery: three questions, three architectures
Understand why a cluster is not a recovery plan, why availability and continuity are not designed at the same moment, and how to derive technical objectives from a business BIA instead of inventing them.
Learning objectives
- Distinguish high availability, continuity and recovery
- Derive technical RTOs from business RTOs
- Position ICT readiness within the overall arrangements
- Recognise architectures and their limits
Intended audience
- Infrastructure teams
- Architects
- Project managers
- CISOs
Prerequisites
- None
Detailed curriculum
Module 1
Three different questions
What each arrangement addresses, and what none of them addresses.
Module 2
What technology does not settle
Entitlements, external dependencies and documentation: the three non-technical failure causes.
Assessment method
Self-check questions throughout the lessons, with no recorded score. Where an associated track leads to a certification, that certification has a separate exam.
Document issued
This course does not, on its own, lead to a certificate. A track certification, where one exists, is issued after its exam is passed.
Continuity & Resilience editorial team