Recovery
Recovery is a process or technique for restoring or maintaining an acceptable state or operation after an error, failure, disruption, or degradation.
Rearchitecting LLMs
A recovery process is a post-restructuring procedure that restores or improves a model’s performance after substantial structural components have been removed.
- How it is used
- Restores performance after structural pruning while supporting a smaller model for the target task.
- How deep it goes
- Walks through candidate selection, distillation settings, timing, and validation, with an exercise varying the recovery budget.
- Examples
- Compares four block-pruning candidates and tests recovery of an attention-pruned model with a Paris generation prompt.
- What you can do after
- Apply it via OptiPFair knowledge distillation and evaluate recovered models using benchmarks and direct generation checks.
Fundamentals of Cybersecurity
Recovery is an incident-response activity that restores affected systems to normal operation and applies measures to prevent recurrence.
- How it is used
- Restores affected systems after an incident and applies long-term measures to prevent recurrence.
- How deep it goes
- Explains recovery's place after containment and eradication, with evidence-preservation guidance, but does not specify a system-by-system restoration procedure.
- Examples
- Uses malware isolation and backup-based restoration after system failure or data corruption as practical situations.
- What you can do after
- Practice/perform recovery by restoring affected systems after eradication and applying long-term fixes to reduce recurrence.
Akka in Action, Second Edition
A recovery strategy is a planned response that restores operation or limits the effects of a fault or failure.
- How it is used
- Frames distributed-system failure handling as planned containment, continuation, replacement, reboot, or deliberate shutdown.
- How deep it goes
- Defines recovery strategies and compares several mechanisms, then sketches supervisor decisions without detailing implementation internals.
- Examples
- Uses unavailable networks and services, failed servers or disks, and an Akka application supervised across components.
- What you can do after
- Operate/configure supervisor responses that continue, restart, stop, isolate, replace, or reboot components after failure.
Elixir in Action, Third Edition
Error detection and recovery is a set of mechanisms for identifying failures and restoring affected computation or service.
- How it is used
- Deploys failure detection and supervised restarts to keep server-side services reliable and independently manageable.
- How deep it goes
- Explains supervision hierarchy, startup and shutdown, restart boundaries, escalation, and restart-frequency limits.
- Examples
- Uses a database-worker crash, a nested service tree, and a comparison of two web-server technology stacks.
- What you can do after
- Operate supervised services by reasoning about failure propagation, restarting workers, terminating child services, and escalating recovery.
Read how Elixir in Action, Third Edition explains recovery →
Build Financial Software with Generative AI (From Scratch)
A recovery action is a prescribed response for handling or restoring a condition after an error or exception.
- How it is used
- Provides users with actionable guidance for handling ACH exceptions and can surface that guidance alongside exception details.
- How deep it goes
- Defines code-linked storage and follows options through retrieval and display, while leaving broader help expansion open.
- Examples
- Uses corrected-file requests for codes 001 and 002 and a new File ID Modifier for code 004.
- What you can do after
- Apply via SQL and the exception-details interface to store code-specific guidance and display it when available.
Read how Build Financial Software with Generative AI (From Scratch) explains recovery →
AI for Everyday IT
Database recovery is the process of restoring database data and operation after failure, corruption, or other disruption.
- How it is used
- Safeguards database environments through recoverability planning and supports data recovery decisions during crises.
- How deep it goes
- Explains recovery’s importance and related maintenance guidance but does not detail recovery procedures.
- Examples
- Uses maintenance prompts about backups and DR testing, plus a ransomware crisis plan that includes data recovery.
- What you can do after
- Evaluate backup and maintenance strategies regularly and include data recovery in crisis planning.
Designing AI Systems
Crash recovery is the detection and re-dispatch of work whose executing process or container has unexpectedly disappeared.
- How it is used
- Coordinates reliable asynchronous workflow execution when processes, containers, or individual services fail.
- How deep it goes
- Defines durable job fields and access patterns for orphan detection and re-dispatch, but does not detail the recovery worker algorithm.
- Examples
- Uses a patient-intake multi-step workflow and an asynchronous research job whose container disappears during processing.
- What you can do after
- Operate/configure durable job storage so orphaned work can be identified and re-dispatched without losing its client-visible job identity.
Think Distributed Systems
Recovery is a technique for restoring a system or transaction to an acceptable state after failure or interruption.
- How it is used
- Frames recovery as the transition from an illegal state to a legal state after failure or interruption.
- How deep it goes
- Explains restart logs, idempotent Undo, and state-dependent REDO or UNDO, while showing that coordinator failure can block progress.
- Examples
- Uses crash restart, Transaction Undo Logs, participant failures, coordinator failure, and state-specific recovery actions.
- What you can do after
- Diagnose/debug with it by tracing persistent transaction state and selecting restartable Undo, REDO, abort, or coordinator inquiry.
Architecting for Autonomy
A defined process for correcting, compensating for, or reversing the effects of an erroneous or failed action.
- How it is used
- Frames recovery as an architectural concern for correcting or compensating for failed enterprise actions.
- How deep it goes
- Traces a high-stakes transaction through legal recovery, but does not specify a technical compensation procedure.
- Examples
- Uses Citi’s mistaken $894 million payment and lenders’ refusal to return some funds.
- What you can do after
- Evaluate whether intended effects, approved instructions, executed transactions, and recovery paths remain aligned.
Designing AI Agents
The process of restoring a system or its operation after a failure or interruption.
- How it is used
- Restores progress in agent workflows after failures while controlling uncertain external effects and repair authority.
- How deep it goes
- Details reconciliation states and a bounded repair loop, including verification, rollback, stopping conditions, and handoff.
- Examples
- Uses an unrecorded backfill-job receipt and a sandbox tool call with an invalid argument to illustrate recovery.
- What you can do after
- Practice bounded recovery by reconciling uncertain effects, verifying authorized repairs, and escalating unresolved failures.
Also covered in
- Architecting an Apache Iceberg Lakehouse
- Building User-Friendly DSLs
- JavaScript in DepthIn early access (MEAP)
- Grokking Web Application Security
- Data-Driven Cybersecurity
- Road to Kubernetes
- AI Model EvaluationIn early access (MEAP)
- Latency
- 100 C++ Mistakes and How to Avoid Them
What to know first
- tool useTool use is the capability of an AI system or agent to request external software operations through defined interfaces to obtain information or perform actions.
- contractA contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
- backup and restoreBackup and restore is the practice of preserving copies of data or system state and using them to recover it after loss, damage, or failure.
- communication planA communication plan is a documented arrangement specifying what information is communicated to which audiences, through which channels, and when.
Related concepts
- incident responsepart of · Incident response is the organized process of detecting, investigating, containing, resolving, and recovering from disruptive or harmful events.
- disaster recoverypart of · Disaster recovery is the planning and execution of processes for restoring systems, data, and services after a disruptive event.
- journaluses · A journal is a record that accumulates entries over time, often in sequence, for later reference or review.
Questions about recovery
What is recovery?
Recovery is a process or technique for restoring or maintaining an acceptable state or operation after an error, failure, disruption, or degradation.
Which Manning books explain recovery?
Rearchitecting LLMs, Fundamentals of Cybersecurity, Akka in Action, Second Edition, Elixir in Action, Third Edition, Build Financial Software with Generative AI (From Scratch), AI for Everyday IT, Designing AI Systems, Think Distributed Systems and 2 more.
What should I know before learning recovery?
Manning books that teach recovery usually introduce tool use, contract, backup and restore and communication plan first.
What is recovery part of?
Recovery is part of incident response. Incident response is the organized process of detecting, investigating, containing, resolving, and recovering from disruptive or harmful events.
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.









