Databases
AuraScore 81/100

Real Estate Lease Data Backup Recovery Audit Checklist

Verify high availability, snapshot integrity, and failover preparedness for multi-tenant commercial real estate databases.

Use this checklist during periodic reliability reviews or pre-audit certifications for asset management database clusters. It validates RPO and RTO thresholds across live asset records.

Template

Role: Lead Database Reliability Engineer specializing in enterprise compliance and business continuity for real estate portfolios.

Context

  • Primary Cluster: {{primary_cluster_name}}
  • Disaster Recovery Region: {{secondary_region}}
  • Target RPO: {{target_rpo_minutes}} minutes
  • Target RTO: {{target_rto_minutes}} minutes
  • Compliance Standard: {{compliance_framework}}
  • Retention Policy: {{retention_period_days}} days

Task

Generate an audit checklist to verify automated backups, write-ahead log shipping, and point-in-time recovery capabilities for {{primary_cluster_name}} to meet {{compliance_framework}} requirements.

Method

  1. Review continuous WAL archiving and snapshot frequencies from {{primary_cluster_name}} to {{secondary_region}}.
  2. Verify immutable backup storage locks and encryption keys to satisfy the {{retention_period_days}}-day policy.
  3. Outline the restoration drill steps to spin up an isolated test instance in {{secondary_region}}.
  4. Measure automated restore durations to validate compliance with the {{target_rto_minutes}}-minute RTO.
  5. Audit point-in-time recovery (PITR) transaction consistency against the {{target_rpo_minutes}}-minute RPO.
  6. Validate automated health checks, split-brain protection, and DNS failover record TTLs.
  7. Inspect alerting thresholds for failed snapshot generation and replication stream disconnects.
  8. Formulate an evidence log format to document audit compliance for {{compliance_framework}}.

Constraints

  • MUST test actual restoration from archive rather than relying solely on backup job exit codes.
  • MUST NOT execute destructive failover tests against active production traffic on {{primary_cluster_name}}.
  • Every verification step must define an auditable artifact or command output.
  • RPO and RTO thresholds MUST reflect {{target_rpo_minutes}}m and {{target_rto_minutes}}m limits strictly.

Output format

Provide a comprehensive audit checklist formatted into four logical sections: '1. Archival & Storage Policy Audit', '2. Point-in-Time Recovery Drill', '3. Regional Failover Configuration', and '4. Compliance Evidence Generation'. Present each item with an audit check ID, validation command, acceptable criteria, and sign-off status box. Include 12 to 16 total audit points.

Self-review

  • Confirm that {{secondary_region}} is explicitly incorporated in failover steps.
  • Check that the {{retention_period_days}}-day retention rule is verified in storage checks.
  • Ensure RPO/RTO calculations align directly with {{target_rpo_minutes}} and {{target_rto_minutes}}.
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 engineering12/12 · Strong

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 efficiency5/10 · Thin

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
real-estate-construction
disaster-recovery
backup-audit
real-estate