Backup disaster recovery automation strategies

🎭 Role

Act as a Senior Site Reliability Engineer (SRE) and Disaster Recovery Architect with over 15 years of experience in enterprise-grade infrastructure, high-availability systems, and regulatory compliance. Your expertise lies in designing automated, self-healing, and immutable backup architectures that guarantee business continuity under extreme failure scenarios.

🌐 Context

We are architecting a resilient data protection framework for [ORGANIZATION_NAME], which currently operates on a [HYBRID/CLOUD-NATIVE/ON-PREM] infrastructure. The objective is to transition from manual, legacy recovery processes to a fully automated, auditable, and scalable Disaster Recovery (DR) posture that meets stringent RTO/RPO targets while ensuring data sovereignty and integrity.

🛠️ Task Instruction

Design a comprehensive, enterprise-level Backup and Disaster Recovery (BDR) Automation Strategy. Please structure the response based on the following modules:

1. Architecture Foundation: Apply the 3-2-1 backup methodology tailored to [PRIMARY_STACK_TECHNOLOGY]. Define how to reconcile Full, Incremental, and Differential backup schedules to optimize for storage efficiency and recovery speed.
2. Automated Workflows:
   • Database Layer: Detail scripts/tools for automated point-in-time recovery (PITR) and transaction log shipping.
   • Filesystem & Application: Specify tools (e.g., rsync, duplicity, or native cloud snapshots) for encrypted, state-consistent backups.
3. Cloud-Integrated Orchestration: Provide a strategic implementation guide for [CHOSEN_CLOUD_PROVIDER: AWS/Azure/GCP], specifically leveraging their native backup vaults, lifecycle policies, and automated compliance reporting.
4. Disaster Recovery Orchestration: Outline an automated failover workflow, including DNS propagation management, load balancer reconfiguration, and database primary/secondary promotion.
5. Validation & Compliance: Design an automated verification suite that includes checksum-based integrity checks and periodic "restore-to-sandbox" testing to ensure RTO < [X] hours and RPO < [Y] hours.
6. Observability: Define the alerting and monitoring framework, specifically for success/failure thresholds, storage consumption forecasting, and audit trail generation for regulatory compliance (e.g., [RETENTION_PERIOD] years).

⚖️ Constraints & Tone

• Tone: Technical, authoritative, prescriptive, and professional.
• Length: Provide deep-dive technical explanations without unnecessary fluff.
• Prohibitions: Do not suggest manual intervention workflows; prioritize "Infrastructure as Code" (IaC) and automation-first approaches. Do not overlook security; ensure encryption at rest and in transit are mentioned in every section.

📝 Output Format

• Use Markdown for readability.
• Include a "Summary Table" comparing RTO/RPO targets against proposed toolsets.
• Use code blocks for pseudocode or configuration examples where appropriate.
• Organize by clear headers.

Placeholders

• [ORGANIZATION_NAME]: Name of the entity.
• [HYBRID/CLOUD-NATIVE/ON-PREM]: Infrastructure environment.
• [PRIMARY_STACK_TECHNOLOGY]: Primary databases or platforms (e.g., PostgreSQL, Kubernetes, SAP).
• [CHOSEN_CLOUD_PROVIDER]: Target environment (AWS, Azure, or GCP).
• [X] hours / [Y] hours: Specific recovery objectives.
• [RETENTION_PERIOD]: Required years for legal/compliance.