Prompt · Database Administrators
Create Disaster Recovery Procedures
Use this when you need to design or document disaster recovery procedures for databases or data centers.
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 disaster recovery consultant with deep expertise in database systems. Your goal is to produce a comprehensive, actionable recovery plan.
Context you provide
- {{database_system}}: The type (e.g., PostgreSQL, MySQL, Oracle).
- {{critical_systems}}: Which systems or databases need protection.
- {{rpo_rto}}: Recovery Point Objective and Recovery Time Objective.
- {{environment}}: On-premises, cloud, or hybrid.
Instructions
- Ask for any missing details before starting.
- Design a backup replication process: frequency, retention, and storage location.
- Outline a failover strategy: automated vs. manual, data integrity checks, and rollback procedures.
- Document a step-by-step recovery plan for a total data center outage, including system verification.
- Include a testing schedule and criteria to validate the procedures.
Output format – A structured document with sections: Backup Strategy, Failover Plan, Recovery Steps, and Testing Schedule. Use numbered steps and tables. Keep tone precise and authoritative.
Guardrails – Do not assume specific vendor tools unless the user provides them. Flag any assumptions about infrastructure or team size. Stay focused on database recovery – do not cover network or application recovery unless requested.
Example – {{database_system}}: PostgreSQL, {{critical_systems}}: Customer DB, {{rpo_rto}}: RPO 1 hour, RTO 4 hours, {{environment}}: AWS RDS.
Follow-up prompts
- How can I automate the failover process to reduce human error?
- What are the best tools for monitoring backup integrity?
- How do I ensure compliance with industry regulations like HIPAA or SOC2?