Databases
AuraScore 81/100

Distributed Generation Database Failover Readiness Checklist

Validate disaster recovery replication, failover latency, and client rerouting for renewable asset state databases.

Use this template prior to scheduled disaster recovery drills or operational failover tests for distributed generation control backends. It verifies replication health, data loss thresholds, and connection recovery under grid resilience mandates.

Template

Role: Lead Energy Infrastructure Database Administrator overseeing distributed generation and microgrid state stores.

Context

  • Generation asset portfolio: {{generation_asset_type}}
  • Primary database architecture: {{primary_cluster_topology}}
  • Disaster recovery site: {{standby_region}}
  • Maximum recovery point objective: {{rpo_target_seconds}}
  • Target recovery time objective: {{rto_target_minutes}}
  • Reliability mandate: {{compliance_standard}}

Task

Create a failover readiness and disaster recovery validation checklist for the mission-critical database cluster managing operational telemetry and dispatch commands for {{generation_asset_type}}.

Method

  1. Measure continuous replication lag between {{primary_cluster_topology}} and {{standby_region}}.
  2. Simulate network split scenarios to verify automatic leader election without split-brain anomalies.
  3. Audit client connection pool redirection and DNS time-to-live settings for generation dispatch services.
  4. Verify write consistency and sequence reconciliation against {{rpo_target_seconds}} during induced primary failure.
  5. Benchmark restart and recovery duration against the allowed limit of {{rto_target_minutes}}.
  6. Validate that automated failover playbooks satisfy auditing requirements under {{compliance_standard}}.
  7. Confirm post-failover reverse synchronization back to the primary site after recovery.

Constraints

  • MUST enforce failover validation criteria strictly adhering to {{rpo_target_seconds}} and {{rto_target_minutes}}.
  • MUST NOT execute destructive actions without explicit pre-flight replication health verification.
  • Every checklist task must provide an explicit pass/fail threshold and diagnostic query.
  • Limit scope to operational resilience, database replication, and client failover routing.

Output format

  • Section 1: Pre-Drill Replication Health & Topology Checklist (4 binary validation points)
  • Section 2: Controlled Failover Execution & Timing Checklist (5 chronological verification steps)
  • Section 3: Post-Failover Integrity & Client Reconnect Checklist (4 verification items with expected metrics)

Self-review

  • Ensure both {{rpo_target_seconds}} and {{rto_target_minutes}} metrics are explicitly tested in the checklist.
  • Verify that {{compliance_standard}} requirements are integrated into post-test auditing.
  • Check that the steps address failover for {{generation_asset_type}} systems specifically.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-databases
energy-utilities
failover
disaster-recovery
renewables