PECB Certified Lead Disaster Recovery Manager key terms

The maximum acceptable elapsed time to restore a process, system, or service after a disruption before the impact becomes unacceptable. It sets the target speed for recovery and drives strategy selection and testing criteria.

The maximum acceptable amount of data loss measured in time before a disruption, expressed as how far back the last usable copy may be. It determines backup frequency and replication design.

The longest time a disruption of an activity can last before its impacts become unacceptable to the organization. It is derived from impact analysis and caps the RTO that a recovery strategy may accept.

A structured process that identifies time-critical activities and quantifies how disruption affects them over time, across financial, legal, regulatory, operational, and reputational dimensions. It produces recovery priorities, RTOs, RPOs, and minimum resource requirements.

The process of identifying threats and vulnerabilities relevant to the organization, then analyzing and evaluating the resulting risk against defined criteria. In disaster recovery it determines which scenarios the program must plan for and how strategies are prioritized.

The selection and application of options to modify risk, such as avoiding, reducing, transferring, or accepting it. Disaster recovery strategies are one form of treatment aimed at reducing the likelihood or consequence of disruptive events.

The risk that remains after controls and recovery capabilities have been applied. It must be compared with the organization's risk acceptance criteria and formally accepted by an accountable owner.

A holistic management process that builds organizational resilience to disruptions through capability for prevention, response, and recovery. Disaster recovery is the part of BCM focused on restoring technology and supporting infrastructure.

The capability and set of arrangements used to restore critical technology services, data, and supporting infrastructure after a major disruption within agreed time and data-loss targets. It focuses on IT and dependent facilities rather than the whole business.

Documented procedures that guide an organization in responding to and continuing or restoring business activities during and after a disruption. It coordinates people, communications, facilities, and processes, of which the IT recovery plan is one component.

A documented set of procedures, roles, and resources for recovering critical IT systems, data, and infrastructure after a disruption. It translates recovery strategies into sequenced, executable actions with owners and dependencies.

The chosen approach for recovering prioritized services, such as backup and restore, warm standby, or active-active, selected by weighing recovery targets against cost, risk, and feasibility. It defines the architecture and arrangements that the plan later operationalizes.

The ongoing organizational structure of governance, resources, processes, and improvement activities that keeps recovery capability effective over time. It spans initiation, risk analysis, strategy, planning, testing, and maintenance rather than a single project.

A top-management statement defining the organization's commitment, objectives, scope, principles, and accountability for disaster recovery. It authorizes the program and provides the criteria against which recovery capability is governed and reviewed.

A senior executive who provides authority, funding, and visible support for the disaster recovery program and removes organizational obstacles. The sponsor holds ultimate accountability for accepting residual risk and approving recovery targets.

A cross-functional governance body that oversees the disaster recovery program, resolves prioritization conflicts, approves strategies and budgets, and monitors progress. It typically includes business, IT, risk, and compliance representation.

The amount and type of risk an organization is willing to accept in pursuit of its objectives. It guides how much investment in recovery capability is justified and which recovery targets are acceptable.

A business process or supporting service whose disruption would cause unacceptable impact within a defined time, based on BIA findings. Critical activities receive priority in recovery sequencing and resource allocation.

The identification and documentation of relationships between business activities, applications, data, infrastructure, suppliers, and people that recovery relies upon. It reveals hidden single points of failure and determines correct recovery sequencing.

A component, resource, or supplier whose failure alone can disrupt a critical service because no redundancy or alternative exists. Identifying these drives targeted resilience investment and recovery strategy design.

A designated alternate location or environment where critical systems and operations can be restored after a disaster. Options range from cold and warm sites to hot sites and cloud-based regions, each with different cost and recovery speed.

A fully equipped alternate facility or environment with hardware, software, data, and network ready to take over operations with minimal delay. It supports very short recovery times but carries the highest ongoing cost.

An alternate environment with some pre-installed infrastructure and partial data that requires configuration and data restoration before operations resume. It balances cost against moderate recovery times.

A basic alternate facility providing space, power, and connectivity but no pre-installed systems or current data. Recovery requires substantial setup time, making it suitable only for activities with long tolerable disruption periods.

A recovery strategy that copies data and systems to separate media so they can be reinstated after loss or corruption. Its achievable RTO and RPO depend on backup frequency, retention, restoration speed, and tested integrity.

The continuous copying of data from one location or system to another so a usable copy exists if the primary fails. Synchronous replication minimizes data loss while asynchronous replication tolerates latency over distance.

A resilient architecture in which two or more sites or systems process workload simultaneously, so failure of one shifts traffic to the others with little or no interruption. It offers the fastest recovery but demands significant cost and operational maturity.

A resilient architecture in which a standby site or system remains idle or partially loaded until the primary fails, then takes over. It costs less than active-active but requires a tested failover process and tolerates some interruption.

The process of transferring operations from a failed or degraded component or site to a redundant one. It must be automated or rehearsed, and its duration contributes directly to the achieved recovery time.

The planned return of operations from the recovery environment to the restored primary environment. It requires reconciliation of data and configuration, and is often more complex and risky than the original failover.

The deliberate duplication of components, paths, data, or capacity so that a single failure does not interrupt service. It is a core design principle for meeting aggressive recovery objectives.

The arrangements for leading and coordinating the organization during a major disruption, including decision-making, escalation, and stakeholder communication. It complements technical recovery by managing the wider organizational response.

The structured process for detecting, containing, eradicating, and recovering from security or operational incidents. It may trigger disaster recovery when impact exceeds defined thresholds.

A designated physical or virtual location where the response team assembles to coordinate decisions, communications, and recovery activities during a disruption. It centralizes information flow and authority.

A detailed, step-by-step operational guide for executing a specific recovery procedure, including prerequisites, commands, validation checks, and escalation contacts. Runbooks make plans executable by staff under pressure.

A discussion-based test in which participants walk through a simulated disruption scenario to validate plans, roles, and decision-making without activating systems. It is low cost and effective for revealing gaps in coordination and assumptions.

Planned activities that verify recovery plans, strategies, and resources actually work and meet defined targets. Testing ranges from plan reviews and tabletops to full failover exercises and should follow a documented schedule.

The most rigorous form of DR testing, in which production operations are actually moved to the recovery environment and back. It provides the strongest evidence of capability but carries the highest risk and requires careful controls.

The structured review after a test or real incident that identifies what worked, what failed, and what must change. Findings feed corrective actions into plan updates and program improvement.

A documented change made to eliminate the cause of a detected deficiency in plans, capabilities, or controls. Each action should have an owner, a due date, and verification of completion.

The measured level of sophistication and effectiveness of an organization's recovery capability, typically assessed against a staged model. It reflects governance, planning, testing frequency, and continuous improvement rather than document existence alone.

The ability of an organization and its systems to anticipate, absorb, adapt to, and recover from disruption. It combines preventive design, continuity arrangements, and recovery capability.