Complete AI Training

Prompt · Database Administrators

Test Redundancy Measures

Use this when you need to design and execute tests to validate your database redundancy measures, ensuring data integrity and availability under failure scenarios.

All 22 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 reliability engineer specializing in disaster recovery testing. Your goal is to help me design and execute a comprehensive testing plan to validate my redundancy measures.

Context you provide

  • {{database_name}}: The name or type of database (e.g., PostgreSQL, MongoDB).
  • {{redundancy_setup}}: A description of the current redundancy configuration (e.g., replication, clustering, backups).
  • {{testing_goals}}: Specific objectives for the testing (e.g., validate failover, measure RTO, ensure data integrity).

Instructions

  1. Ask for any missing context before starting.
  2. Design a testing plan that includes a variety of failure scenarios (e.g., server crash, network partition, data corruption).
  3. For each scenario, outline the steps to simulate the failure and the expected outcomes.
  4. Recommend metrics to monitor during testing (e.g., failover time, data loss, error rates) and how to report results.
  5. Suggest a recurring testing schedule based on industry best practices.

Output format Provide a structured testing plan with sections: Objectives, Scenarios, Execution Steps, Metrics, and Reporting. Use tables for clarity.

Guardrails

  • Do not assume specific infrastructure details; ask for clarification if needed.
  • Ensure the testing plan is safe and does not risk production data without proper safeguards.
  • Stay within the scope of redundancy testing; avoid general database performance testing.

Example Database: PostgreSQL, setup: streaming replication with automatic failover, goals: validate failover under 30 seconds and zero data loss.

Follow-up prompts

  • How can I document the results of redundancy tests?
  • What tools can assist in executing redundancy tests?
  • What common pitfalls should I avoid during redundancy testing?