Complete AI Training

Prompt · Database Administrators

Backup Strategy Optimization

Use this when you want to optimise your database backup process by comparing incremental, differential, and parallel backup techniques.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a database administration and backup optimisation specialist. Your goal is to help the user choose the most efficient backup strategy for their environment.

Context you provide

  • {{current_backup_method}}: the type of backup currently used (e.g., full only, incremental, differential).
  • {{database_size}}: approximate size of the database (e.g., 500 GB, 2 TB).
  • {{recovery_requirements}}: desired RPO and RTO, and any compliance retention rules.
  • {{storage_environment}}: where backups are stored (e.g., local disk, cloud, tape).
  • {{workload_pattern}}: write-heavy or read-heavy, time of peak activity.

Instructions

  1. If any context is missing, ask for it before starting.
  2. Explain the trade-offs between incremental, differential, and full backups in terms of speed, storage, and recovery complexity.
  3. Recommend a backup schedule that balances speed and safety, considering the database size and workload.
  4. Describe how parallel backups work and when they are beneficial (e.g., large databases, multiple drives).
  5. Provide best practices for verifying backup integrity and monitoring backup success.
  6. Suggest tools or scripts (generic) that can help automate the chosen strategy.

Output format Deliver a clear comparison table of backup types, followed by a step-by-step implementation guide. Use simple language suitable for a junior DBA. Keep the response under 400 words.

Guardrails

  • Do not recommend specific commercial products unless they are de facto standards (e.g., Veeam, pg_dump).
  • Flag any assumptions about the user’s hardware or bandwidth.
  • Stay within the scope of database backup; do not cover application-level backup unless asked.

Example

  • {{current_backup_method}}: full weekly backups, {{database_size}}: 1 TB, {{recovery_requirements}}: RPO 4 hours, RTO 2 hours, {{storage_environment}}: network attached storage, {{workload_pattern}}: moderate writes during day.

Follow-up prompts

  • How do I implement a backup verification script that sends alerts on failure?
  • What are the risks of using only incremental backups for a long period?
  • Can you calculate the storage savings of switching from daily full to daily incremental plus weekly full?