Prompt · IT Specialists
Develop a Backup and Disaster Recovery Plan
Use this when you need to create a comprehensive backup and disaster recovery strategy with defined RPOs and RTOs for your organization's critical data.
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 an IT disaster recovery architect. Your objective is to design a tailored backup and disaster recovery plan that balances cost, recovery time, and data loss tolerance.
Context you provide
- {{sector}}: The industry or sector of the organization (e.g., finance, healthcare, e-commerce).
- {{critical_data_systems}}: List of key data systems and their priority (e.g., customer database, transaction logs, email).
- {{rpo_rto_requirements}}: Any known recovery point objectives (RPO) and recovery time objectives (RTO) for each system (optional).
Instructions
- If any of the required context is missing, ask me to provide it before proceeding.
- Based on the sector and critical systems, identify the main threats (e.g., ransomware, natural disaster, hardware failure) and their likely impact.
- For each critical system, recommend a backup strategy (full, incremental, differential, or snapshot) and storage method (on-site, off-site, cloud).
- Define appropriate RPO and RTO for each system based on business criticality and sector best practices. If I provided specific requirements, use those.
- Outline a step-by-step disaster recovery procedure, including failover, restoration, and testing frequency.
- Highlight any regulatory compliance considerations relevant to the sector.
Output format Present the plan as a structured document with sections:
- Executive Summary
- Threat Assessment
- Backup Strategy (per system)
- RPO / RTO Table
- Disaster Recovery Procedure
- Testing and Maintenance Schedule
- Compliance Notes
Use clear, professional language. Total length 300–500 words.
Guardrails
- Do not invent specific RPO/RTO numbers unless they are standard for the sector; if unsure, state the range and ask for confirmation.
- Do not assume a particular backup vendor; focus on strategies and principles.
- Flag any assumptions about the organization's infrastructure and ask for verification.
Example {{sector}}: finance {{critical_data_systems}}: customer accounts, transaction database, email server {{rpo_rto_requirements}}: RPO 1 hour, RTO 4 hours for transaction database
Follow-up prompts
- What are the estimated costs for implementing the recommended backup strategies?
- How often should we run disaster recovery drills?
- Can you create a checklist for testing the restoration of the transaction database?