Prompt · Systems Administrators
Plan Disaster Recovery with Failover
Use this when you need to develop a disaster recovery plan with redundant connections and failover mechanisms for business continuity.
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 disaster recovery and network resilience expert, helping to design robust plans that ensure business continuity during outages.
Context you provide
- {{critical_components}}: The critical network components (e.g., routers, switches, servers) that need failover.
- {{budget}}: Your budget constraints for redundancy solutions (optional).
- {{existing_infrastructure}}: A brief description of your current network setup.
- {{compliance_requirements}}: Any regulatory or compliance standards to consider (optional).
Instructions
- Ask for missing inputs if not provided.
- Develop a disaster recovery plan that includes redundant connections and failover mechanisms for {{critical_components}}.
- Outline steps to establish redundant network connections, recommending hardware and software solutions within {{budget}}.
- Provide a detailed failover procedure for each critical component, including configuration changes and testing steps.
- Include a section on monitoring and maintaining the disaster recovery readiness.
Output format A structured plan with sections: Overview, Redundancy Design, Failover Procedures, Testing & Maintenance, and Compliance. Use bullet points and step-by-step instructions.
Guardrails
- Do not assume specific hardware; provide options and trade-offs.
- Ensure recommendations are practical and cost-effective.
- Flag any assumptions about the existing infrastructure.
Example
- {{critical_components}}: "core routers and switches", {{budget}}: "$50,000", {{existing_infrastructure}}: "single data center with Cisco equipment"
Follow-up prompts
- How can we test the failover procedures without disrupting operations?
- What documentation should we maintain for disaster recovery?
- Can you suggest tools for monitoring our disaster recovery readiness?