Disaster Recovery Overview
Model recovery dependencies, capacity, objectives and scenarios before a real incident.
Recovery assessment
Workload recovery timeline
How to interpret results
Times are planning estimates based on entered data volume, bandwidth, overhead, startup time, dependencies and parallel recovery slots. Results are not measured restore tests or guarantees. RPO is assessed only when a verified backup age is supplied.
Workloads & dependencies
Set critical systems, restore size, startup time, RTO/RPO targets, and prerequisite workloads.
| System / service | GB to restore | Start-up min | RTO h | RPO h | Last verified backup age h | Depends on (IDs) | Critical |
|---|
Dependency IDs appear beneath workload names. A workload starts recovery only after its dependencies finish. Cycles and missing IDs are reported as validation errors.
Recovery scenario simulator
Compare resource constraints, disruptions and recovery approaches.
Recovery environment
Scenario findings
Recovery dependency map
Generated from your workload dependencies and estimated recovery order.
Recovery runbook
Dependency-aware recovery order and practical validation steps. Review and customize for your environment.
Retention & storage estimator
Estimate storage requirements from recovery-point frequency and backup assumptions.
Retention policy
Storage estimate
Recovery-site capacity
Compare declared recovery VM requirements against available CPU, memory, and storage after headroom.
Available site capacity
Workload resources
| Workload | vCPU | RAM GB | Storage GB |
|---|
Restore test evidence
Record measured restoration timestamps. Only reviewer-verified tests are compared to objectives.
New restore test
Restore test history
Business impact estimator
Approximate downtime exposure with transparent assumptions. Values are not audited financial losses.
Reports & project backups
Export a complete project, restore it later, or share a standalone assessment.
Project details
Exports
Project JSON includes all entered workload information. Review content before sharing. PDF uses your browser's Print → Save as PDF.
Validation & limitations
Recovery times assume the entered data can be transferred at the modeled effective throughput and that recovery work consumes one slot at a time. They do not emulate backup software, actual cloud APIs, failover cluster behavior or live systems. Storage bottleneck is modeled as a throughput cap per active restore; shared contention may increase real recovery times.
Sites, failover & replication
Plan recovery targets and quantify replication-link feasibility using transparent estimates.
Sites
| Site name | Role | WAN Mbps | Available vCPU | Available RAM GB | Storage GB |
|---|
Workload recovery & replication assignments
| Workload | Recovery site | Mode | Daily changed GB | Replica lag h | Startup overhead min |
|---|
Replication feasibility assessment
Recovery scenario comparison
Compare site-specific failure cases against the baseline recovery plan.
Multi-site recovery diagram
Automatically generated from sites and workload assignments.
Logical illustration, not discovered cabling, routing, or actual replication validation.
Technical disaster recovery design
Report built from your project, site allocations, recovery objectives, and identified gaps.
DR Test & Failover Orchestration Planner
Plan cutovers, model aggregate replication, review capacity and retain evidence. This tool does not perform real failover.
Network & DNS cutover assumptions
Failover execution checklist
Aggregate replication and recovery-site capacity
Failback checklist
Record DR orchestration test
Orchestration test history
Estimated timings do not verify successful DR, DNS propagation, or data integrity. Test verification must be based on external evidence.
DR Readiness & Audit Intelligence
Prioritize recovery gaps, track evidence freshness and compare disaster planning scenarios.
Prioritized findings
Assessment policy settings
Add evidence reference
Evidence freshness register
Disaster scenario considerations
Assessment uses user-entered evidence; scenario cards except baseline are qualitative and do not prove site recovery. No actual device or backup testing is performed.