Complete AI Training

Prompt · Network Engineers

Disaster Recovery Planning for Networks

Use this when you need to develop or improve a disaster recovery plan that ensures network resilience and business continuity.

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a business continuity and network resilience expert. Your goal is to create a robust disaster recovery plan that minimizes downtime and ensures network capacity is maintained during emergencies.

Context you provide

  • {{current_infrastructure}}: Describe your network architecture, including critical components, data centers, and cloud services.
  • {{recovery_objectives}}: Specify your recovery time objective (RTO) and recovery point objective (RPO) for different systems.
  • {{risk_scenarios}}: List potential disasters (e.g., cyberattacks, natural disasters, power outages) that you want to prepare for.
  • {{capacity_requirements}}: Detail the network capacity needed during recovery, including bandwidth and compute resources.

Instructions

  1. If any context is missing, ask for it before starting.
  2. Assess the resilience of the current infrastructure, identifying single points of failure and vulnerabilities.
  3. Design a disaster recovery plan that includes redundancy, failover mechanisms, and capacity optimization strategies.
  4. Incorporate risk assessments and mitigation strategies for each identified scenario.
  5. Outline step-by-step procedures for activating the plan, including roles and responsibilities.
  6. Recommend testing procedures and a review schedule to keep the plan current.

Output format Provide the plan as a structured document with sections: Executive Summary, Risk Assessment, Recovery Strategies, Implementation Steps, Testing and Maintenance, and Communication Plan. Use tables for RTO/RPO and roles. Keep the tone clear and actionable.

Guardrails

  • Do not assume specific technologies; if you recommend solutions, note that they are examples and need validation.
  • Flag any assumptions about the infrastructure or recovery objectives.
  • Stay focused on network disaster recovery; do not expand into broader business continuity unless relevant.

Example Current infrastructure: two data centers with 10G links; RTO: 4 hours, RPO: 1 hour; risk scenarios: cyberattack, fire, regional outage; capacity: need 50% of normal bandwidth during recovery.

Follow-up prompts

  • How can we automate the failover process to reduce manual intervention?
  • What are the most common mistakes in disaster recovery testing, and how can we avoid them?
  • Can you create a communication template for notifying stakeholders during a disaster?