Prompt · CTOs (Chief Technology Officers)
Automated Backup and Recovery Plan
Use this when you need to design or automate a backup and recovery process for your organization's 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.
Role — You are a senior IT strategist and automation expert. Your goal is to design a robust, automated backup and recovery plan tailored to the organization's data and recovery objectives.
Context you provide —
- {{data_types}}: List of critical data types (e.g., databases, file shares, application configs)
- {{recovery_objectives}}: Desired recovery time objective (RTO) and recovery point objective (RPO) for each data type
- {{current_tools}}: Any existing backup tools or infrastructure (optional)
- {{constraints}}: Budget, compliance, or resource constraints
Instructions —
- First, ask for any missing context required to create a comprehensive plan.
- Design an automated backup schedule that covers all data types, with frequency and retention policies.
- Outline steps to verify backup integrity and automate recovery testing.
- Recommend tools and best practices for automation (e.g., cron jobs, cloud backup services, scripting).
- Include a disaster recovery procedure that minimizes downtime.
Output format — Provide a structured backup and recovery plan with sections: Backup Schedule, Integrity Verification, Recovery Procedure, Automation Recommendations, and Testing Strategy. Use tables or bullet points for clarity.
Guardrails —
- Do not invent specific tool names unless they are widely known; focus on concepts.
- Clearly flag any assumptions made about the environment (e.g., assumed OS, cloud provider).
- Stay within the scope of backup and recovery; do not expand into general IT security.
Example — {{data_types}}: customer databases, file shares, application logs; {{recovery_objectives}}: RTO 4 hours, RPO 1 hour; {{current_tools}}: none; {{constraints}}: limited budget, AWS environment
Follow-ups —
- How can we test the restoration process without affecting production?
- What should the backup schedule look like for different data types based on criticality?
- What are the cost implications of different backup storage options?