Contract
- Input: service inventory, data criticality, compliance requirements, current backup posture, recovery time targets.
- Output: backup and DR architecture + recovery objectives matrix + backup strategy + restore testing plan.
- Scope: designs backup and DR strategy; does not execute production failover or data deletion unless explicitly instructed.
- Rule: designs backup and DR strategy; does not execute production failover or data deletion unless explicitly instructed.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit BackupDisasterRecoveryArtifact as both:
- JSON:
.agents/skills/platform/artifacts/backup-disaster-recovery/{identifier}.json
- Markdown view: same filename with
.md extension
Backup and Disaster Recovery
Design a backup and disaster recovery strategy with explicit recovery objectives (RPO/RTO), backup strategies, restore testing, and cross-region resilience.
Process
1. Frame the backup and DR problem
- Service inventory: databases, object storage, message queues, configuration, secrets, container images.
- Data criticality: tier 1 (transactional, revenue-generating), tier 2 (operational), tier 3 (analytics, logs).
- Compliance: retention requirements (legal, regulatory, contractual), data sovereignty, encryption.
- Current posture: existing backup tools, schedules, retention, restore history, known gaps.
Completion criterion: service inventory documented; criticality tiers defined; compliance requirements stated.
2. Recovery objectives
- RPO (Recovery Point Objective): maximum acceptable data loss per service.
- RTO (Recovery Time Objective): maximum acceptable downtime per service.
- RSL (Recovery Service Level): acceptable degraded mode during recovery.
- Per-service matrix: database RPO/RTO, object storage RPO/RTO, configuration RPO/RTO, message queue RPO/RTO.
- Alignment with business: acceptable downtime per revenue impact; SLA commitments.
Completion criterion: recovery objectives matrix saved with per-service RPO, RTO, and RSL.
3. Backup strategy
- Backup types: full, incremental, differential, continuous (WAL archiving, change data capture).
- Backup scope: data only, data + configuration + secrets, full system snapshot.
- Storage: local (same region), cross-region, off-site, immutable (object lock, WORM).
- Retention: short-term (daily, weekly), long-term (monthly, yearly); legal hold; automated expiry.
- Encryption: encryption at rest; key management; access control for backup storage.
Completion criterion: backup strategy documented with types, scope, storage locations, and retention policy.
4. Cross-region and multi-cloud DR
- Topology: active-active, active-passive, pilot light, warm standby, cold standby.
- Replication: synchronous (zero RPO, high latency), asynchronous (low latency, non-zero RPO), hybrid.
- DNS and traffic routing: failover DNS, anycast, load balancer health checks, split-horizon DNS.
- Data consistency: eventual consistency tolerance; conflict resolution; last-write-wins vs CRDT.
- Cloud provider diversification: multi-cloud DR to avoid single-provider outages.
Completion criterion: cross-region DR topology documented with replication mode and failover trigger.
5. Restore testing and validation
- Testing cadence: quarterly full restore, monthly critical service restore, weekly automated backup verification.
- Test scope: restore to isolated environment; verify data integrity, application functionality, performance.
- Automation: automated restore jobs with pass/fail reporting; synthetic transactions post-restore.
- Documentation: restore runbooks with step-by-step commands, expected duration, rollback on failure.
Completion criterion: restore testing plan documented with cadence, scope, automation, and pass/fail criteria.
6. Failover and runbooks
- Failover triggers: RTO breach, data corruption, regional outage, manual decision.
- Failover process: DNS switch, traffic routing, database promotion, cache warm-up, health checks.
- Communication: incident commander, stakeholder notifications, status page updates.
- Rollback: criteria for returning to primary; data reconciliation post-failback; learning review.
Completion criterion: failover runbook saved with triggers, process, communication plan, and rollback criteria.
Rules
- Rule: define RPO and RTO per service before designing backup or DR topology.
- Rule: store backups in at least two locations, one off-site or cross-region; use immutable storage where possible.
- Rule: test restores regularly; untested backups are not backups.
- Rule: automate backup verification with integrity checks and synthetic post-restore validation.
- Rule: document failover and rollback runbooks with explicit triggers, steps, and communication plans.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "backup-disaster-recovery"3category: "devops"4maturity: "stable"5version: "1"6description: "Design backup and disaster recovery — RPO/RTO, backup strategies, restore testing, cross-region — with explicit recovery objectives and validation."7license: "MIT"8capabilities:9 - apply backup disaster recovery methods within explicit devops boundaries10 - analyze design backup and disaster recovery — rpo/rto, backup strategies, restore testing, cross-region — with explicit recovery objectives and validation with assumptions, constraints, and failure modes11 - produce and validate a devops artifact with evidence, decisions, and next steps12outputs: "backup and DR architecture + recovery objectives matrix + backup strategy + restore testing plan."13sideEffects: []14dependencies: []15stopCondition: "Architecture diagram saved; recovery objectives matrix complete; backup strategy documented; restore testing plan filled."16risk: "medium"17trustTier: "3"18maxIterations: "7"19promptVersion: "2.0"20artifactType: "devops"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/backup-disaster-recovery.json24diataxis: "how-to"25tags: ["devops"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/backup-disaster-recovery31---3233## Contract3435- Input: service inventory, data criticality, compliance requirements, current backup posture, recovery time targets.36- Output: backup and DR architecture + recovery objectives matrix + backup strategy + restore testing plan.37- Scope: designs backup and DR strategy; does not execute production failover or data deletion unless explicitly instructed.38- Rule: designs backup and DR strategy; does not execute production failover or data deletion unless explicitly instructed.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `BackupDisasterRecoveryArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/backup-disaster-recovery/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Backup and Disaster Recovery6465Design a **backup and disaster recovery** strategy with explicit recovery objectives (RPO/RTO), backup strategies, restore testing, and cross-region resilience.6667## Process6869### 1. Frame the backup and DR problem70- Service inventory: databases, object storage, message queues, configuration, secrets, container images.71- Data criticality: tier 1 (transactional, revenue-generating), tier 2 (operational), tier 3 (analytics, logs).72- Compliance: retention requirements (legal, regulatory, contractual), data sovereignty, encryption.73- Current posture: existing backup tools, schedules, retention, restore history, known gaps.7475**Completion criterion:** service inventory documented; criticality tiers defined; compliance requirements stated.7677### 2. Recovery objectives78- RPO (Recovery Point Objective): maximum acceptable data loss per service.79- RTO (Recovery Time Objective): maximum acceptable downtime per service.80- RSL (Recovery Service Level): acceptable degraded mode during recovery.81- Per-service matrix: database RPO/RTO, object storage RPO/RTO, configuration RPO/RTO, message queue RPO/RTO.82- Alignment with business: acceptable downtime per revenue impact; SLA commitments.8384**Completion criterion:** recovery objectives matrix saved with per-service RPO, RTO, and RSL.8586### 3. Backup strategy87- Backup types: full, incremental, differential, continuous (WAL archiving, change data capture).88- Backup scope: data only, data + configuration + secrets, full system snapshot.89- Storage: local (same region), cross-region, off-site, immutable (object lock, WORM).90- Retention: short-term (daily, weekly), long-term (monthly, yearly); legal hold; automated expiry.91- Encryption: encryption at rest; key management; access control for backup storage.9293**Completion criterion:** backup strategy documented with types, scope, storage locations, and retention policy.9495### 4. Cross-region and multi-cloud DR96- Topology: active-active, active-passive, pilot light, warm standby, cold standby.97- Replication: synchronous (zero RPO, high latency), asynchronous (low latency, non-zero RPO), hybrid.98- DNS and traffic routing: failover DNS, anycast, load balancer health checks, split-horizon DNS.99- Data consistency: eventual consistency tolerance; conflict resolution; last-write-wins vs CRDT.100- Cloud provider diversification: multi-cloud DR to avoid single-provider outages.101102**Completion criterion:** cross-region DR topology documented with replication mode and failover trigger.103104### 5. Restore testing and validation105- Testing cadence: quarterly full restore, monthly critical service restore, weekly automated backup verification.106- Test scope: restore to isolated environment; verify data integrity, application functionality, performance.107- Automation: automated restore jobs with pass/fail reporting; synthetic transactions post-restore.108- Documentation: restore runbooks with step-by-step commands, expected duration, rollback on failure.109110**Completion criterion:** restore testing plan documented with cadence, scope, automation, and pass/fail criteria.111112### 6. Failover and runbooks113- Failover triggers: RTO breach, data corruption, regional outage, manual decision.114- Failover process: DNS switch, traffic routing, database promotion, cache warm-up, health checks.115- Communication: incident commander, stakeholder notifications, status page updates.116- Rollback: criteria for returning to primary; data reconciliation post-failback; learning review.117118**Completion criterion:** failover runbook saved with triggers, process, communication plan, and rollback criteria.119120## Rules121122- Rule: define RPO and RTO per service before designing backup or DR topology.123- Rule: store backups in at least two locations, one off-site or cross-region; use immutable storage where possible.124- Rule: test restores regularly; untested backups are not backups.125- Rule: automate backup verification with integrity checks and synthetic post-restore validation.126- Rule: document failover and rollback runbooks with explicit triggers, steps, and communication plans.127128## Completion129130- the skill's completion criteria are explicitly checked131- the artifact is saved and validated132- any blockers or skipped validations are documented133- the next consumer is identified or the work is handed off134---135@include .agents/skills/platform/contract-base.xml