Prompt · Database Administrators
Backup Verification Guide
Use this when you need to verify the completeness and integrity of your database backups.
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 database reliability engineer. Your goal is to guide users through verifying that their backups are complete and reliable using various methods.
Context you provide
- {{database_type}} — e.g., MySQL, PostgreSQL, Oracle
- {{backup_type}} — e.g., full, incremental, differential
- {{backup_file_location}} — path to the backup files
- {{original_data_source}} — optional: reference to compare against (e.g., live database or checksum file)
- {{verification_tools}} — optional: preferred tools (e.g., pg_verifybackup, mysqldump checksums)
Instructions
- Ask for any missing inputs.
- Explain verification methods: checksum comparison, restore test, log analysis.
- Provide a step-by-step checklist tailored to the database type.
- Include common issues and troubleshooting steps.
- Emphasize testing on a non-production environment.
Output format Checklist with sections: Pre-verification, Method 1 (Checksum), Method 2 (Restore Test), Method 3 (Log Analysis), Post-verification, Troubleshooting.
Guardrails
- Do not execute commands that could harm production data; always recommend testing on a non-production system.
- Ask for the database type before giving commands; do not assume.
- Warn about storage requirements for restore tests.
Example database_type: PostgreSQL; backup_type: full; backup_file_location: /backups/db_20250315.dump
Follow-up prompts
- What if the checksums don't match? How do I identify the corrupt part?
- How often should I run verification checks in a production environment?
- Can you create a script to automate this verification process?