liveBook · Manning

Disaster recovery

Also called DR

Disaster recovery is the planning and execution of processes for restoring systems, data, and services after a disruptive event.

How 8 Manning books explain it

Think Like a CTO

A disaster recovery strategy is a planned approach for restoring services after a disruptive event by transferring operations to an alternate environment.

How it is used
Plans continuity of client-facing operations when the primary environment fails.
How deep it goes
Works through downtime, reduced service, and switch procedures; stops short of implementation-level instructions.
Examples
Uses fire and network failure scenarios, read-only social posts, and ecommerce browsing without checkout.
What you can do after
Practice/perform a documented recovery switch and test the plan, including how to fail forward or back.

Read how Think Like a CTO explains disaster recovery →

AI for Everyday IT

The process of preparing documented procedures for restoring systems and operations after a disruptive event.

How it is used
Uses generative AI to streamline documentation for restoring services after major disruptions.
How deep it goes
Explains the information needed for a recovery plan through a prompt and response, while deferring real-time plan generation.
Examples
Uses a MySQL administrator’s request for documentation across about 100 servers.
What you can do after
Apply it via Azure OpenAI Service to begin drafting disaster recovery documentation.

Read how AI for Everyday IT explains disaster recovery →

100 SQL Server Mistakes and How to Avoid Them

Disaster recovery is the set of processes and capabilities for restoring systems and data after a disruptive failure or disaster.

How it is used
Distinguishes recovery from high availability so availability planning matches business failure scenarios.
How deep it goes
Defines DR architectures and gives operational testing risks, while deferring actual HA/DR implementation guidance.
Examples
Uses data-center loss, cross-site availability-group failover, inadequate secondary performance, permissions, and encryption misconfiguration.
What you can do after
Evaluate/understand whether a recovery design withstands site loss and requires regular tested failover.

Read how 100 SQL Server Mistakes and How to Avoid Them explains disaster recovery →

Fundamentals of Cybersecurity

Disaster recovery is the process of restoring critical information-technology systems, applications, data, and services after a disruptive event.

How it is used
Restores critical technology after disruptions so essential business operations can continue.
How deep it goes
Explains documented roles, recovery choices, and testing methods, but does not provide a complete system-specific recovery procedure.
Examples
Uses floods, alternate sites, backup restoration, and tabletop exercises to make recovery decisions concrete.
What you can do after
Evaluate/understand recovery plans, site and backup options, and tests for restoring critical technology after disruption.

Read how Fundamentals of Cybersecurity explains disaster recovery →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

Disaster recovery is the set of processes and capabilities for restoring systems and data after a disruptive failure or destructive event.

How it is used
Frames recovery requirements and AWS architectures for virtual-machine, availability-zone, and region-wide failures.
How deep it goes
Defines RTO and RPO, then demonstrates cross-region snapshot copying; it stops short of a complete recovery runbook.
Examples
Uses a WordPress database snapshot copied from us-east-1 to eu-west-1 and a Jenkins server outage to illustrate recovery objectives.
What you can do after
Operate/configure Amazon RDS snapshot commands and evaluate recovery architectures against RTO, RPO, cost, and compliance constraints.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains disaster recovery →

Architecting an Apache Iceberg Lakehouse

Disaster recovery is the set of processes and capabilities for restoring data and system operation after failures, corruption, or other disruptive events.

How it is used
Protects Iceberg lakehouses against metadata loss, file deletion, catalog outages, region failures, and damaging operational changes.
How deep it goes
Explains backup, replication, rollback, reconstruction, monitoring, and orchestrated recovery while stopping short of provider-specific implementation detail.
Examples
Uses catalog backups, metadata.json reconstruction, cross-region replication, snapshot rollback, and recovery DAGs as operational examples.
What you can do after
Build it from scratch by backing up metadata, replicating storage, encoding recovery workflows, and validating snapshot lineage.

Read how Architecting an Apache Iceberg Lakehouse explains disaster recovery →

Microsoft Azure in Action

Disaster recovery is the set of processes and infrastructure used to restore services and data after a catastrophic failure or disruptive event.

How it is used
Protects Azure-hosted services and Banning Books’ ordering database from downtime and data loss.
How deep it goes
Explains backup types, schedules, retention, and point-in-time restoration, but stops short of detailed disaster-response procedures.
Examples
Uses Banning Books’ ordering system, Azure SQL DB backups, and a relational-database comparison to illustrate recovery choices.
What you can do after
Evaluate Azure database choices by comparing disaster-recovery capabilities, cost, security, and potential data loss.

Read how Microsoft Azure in Action explains disaster recovery →

Generative AI in Action

Disaster recovery is the set of processes for restoring systems, data, and services after a catastrophic disruption.

How it is used
Uses disaster recovery to preserve generative AI availability and business continuity during catastrophic disruptions or service failures.
How deep it goes
Frames redundancy, failover, monitoring, and testing, but stops short of specifying recovery procedures, targets, or implementation runbooks.
Examples
Uses redundancy and failover planning, regular testing, monitoring, hyperscaler dependencies, and differing LLM, SLM, and edge scenarios.
What you can do after
Operate/configure production AI deployments with recovery planning linked to availability, monitoring, validation, and failover.

Read how Generative AI in Action explains disaster recovery →

Also covered in

What to know first

Related concepts

Questions about disaster recovery

What is disaster recovery?

Disaster recovery is the planning and execution of processes for restoring systems, data, and services after a disruptive event.

Which Manning books explain disaster recovery?

Think Like a CTO, AI for Everyday IT, 100 SQL Server Mistakes and How to Avoid Them, Fundamentals of Cybersecurity, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, Architecting an Apache Iceberg Lakehouse, Microsoft Azure in Action and Generative AI in Action.

What should I know before learning disaster recovery?

Manning books that teach disaster recovery usually introduce mean, business continuity, infrastructure and outage first.

What is the difference between disaster recovery and business continuity plan?

Disaster recovery is the planning and execution of processes for restoring systems, data, and services after a disruptive event. A business continuity plan is a documented set of strategies, procedures, responsibilities, and resources for maintaining or restoring essential operations during and after a significant disruption.

What is disaster recovery also called?

Disaster recovery is also called DR.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.