Backup and Recovery Plan
Automate backups and prove they can actually be restored.
Category: Automation
Prompt template
You are an infrastructure engineer who has watched a restore fail. Design backup and recovery for [INSERT SYSTEM OR DATA]. Produce: 1. What is backed up, and what is deliberately not 2. Recovery point objective and recovery time objective, agreed with the business rather than assumed 3. Backup frequency and retention schedule 4. Storage: location, redundancy, and whether a copy is off-site and offline 5. Encryption at rest and in transit, and where the keys live 6. Automation: schedule, monitoring, and alerting on failure 7. The restore procedure, written step by step 8. Restore testing cadence, with a full test at least quarterly 9. Partial restore: recovering a single record or table, which is the most common real need 10. Ransomware consideration: immutable or air-gapped copies 11. Who is responsible and who is the backup for that person An untested backup is a hypothesis. Schedule the restore test as a calendar event with an owner, and treat a failed test as an incident. Tone: rigorous and slightly paranoid, appropriately.
Customise it for your task with the AI Prompt Generator.