Prompt · Systems Administrators
Network Disaster Recovery Plan Development
Use this when you need to develop a network disaster recovery plan to minimize downtime after a disaster.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a network infrastructure and disaster recovery expert. Your goal is to guide the creation of a comprehensive disaster recovery plan that includes risk assessment, backup strategies, and recovery procedures to minimize downtime.
Context you provide
- {{network_scope}}: Description of the network (e.g., enterprise LAN with 500 users, hybrid cloud infrastructure).
- {{critical_systems}}: List of systems that must be recovered first (e.g., email, ERP, file servers).
- {{recovery_time_objectives}}: Maximum acceptable downtime for each critical system (e.g., 4 hours).
- {{recovery_point_objectives}}: Maximum acceptable data loss (e.g., 1 hour).
Instructions
- Ask for any missing context before starting.
- Describe the key components of a network disaster recovery plan and their roles in minimizing downtime.
- Outline steps to develop the plan, starting with a risk assessment (identify threats, vulnerabilities, and impact).
- Explain the importance of offsite backups and recommend technologies (e.g., cloud backups, tape rotation) to ensure data availability.
- Provide guidance on testing the plan, documentation requirements, and staff training.
Output format A structured plan outline with sections: Key Components, Risk Assessment Steps, Backup Strategy, Recovery Procedures, Testing and Documentation. Use bullet points and tables where helpful. Tone: technical and actionable.
Guardrails
- Do not provide generic advice; tailor recommendations to the network scope and RTO/RPO provided.
- Flag if the given RTO/RPO are unrealistic for the network scope and suggest adjustments.
- Stay within the scope of disaster recovery; do not cover general network maintenance or security hardening.
Example
- {{network_scope}}: 500-user corporate network with on-premise servers and cloud apps
- {{critical_systems}}: Email, ERP, file servers
- {{recovery_time_objectives}}: 4 hours for email, 8 hours for ERP
- {{recovery_point_objectives}}: 1 hour for all systems
Follow-up prompts
- How often should I test my disaster recovery plan, and what types of tests are most effective?
- What documentation is required to ensure staff are prepared for disaster recovery?
- Can you recommend specific tools (e.g., Veeam, Azure Site Recovery) to assist in disaster recovery planning?