db-backup-recovery
DB Backup Recovery
Overview
Use this skill to define backup and restore behavior that is credible under incident pressure, not only compliant on paper.
Scope Boundaries
- Data loss tolerance and recovery time objectives must be formalized.
- Backup policy is changing due to scale, compliance, or architecture change.
- Teams need confidence that restore procedures actually work.
Core Judgments
- RPO/RTO targets per data class and business workflow.
- Backup modality: full, incremental, log-based, snapshot, or hybrid.
- Retention and immutability policy by legal and business requirements.
- Restore topology: point-in-time restore, region restore, partial table restore.
Practitioner Heuristics
- Start from restore requirements, then derive backup schedule.
- Separate operational backups from archival/legal-retention copies.
- Encryption, key rotation, and access logging apply to backups too.
- Recovery procedures must assume partial infrastructure outage, not ideal environment.
Workflow
- Define data criticality tiers and required RPO/RTO per tier.
- Select backup mechanisms and cadence aligned to write patterns.
- Define retention lifecycle and deletion rules.
- Design restore paths for common and worst-case incident scenarios.
- Establish ownership and escalation for recovery execution.
- Document assumptions that invalidate the current strategy.
Common Failure Modes
- Backup success is monitored but restore path is untested.
- One global retention policy ignores data criticality differences.
- Recovery relies on undocumented manual knowledge.
Failure Conditions
- Stop when RPO/RTO cannot be mapped to concrete mechanisms.
- Stop when backup policy has no feasible restore path.
- Escalate when recovery guarantees exceed infrastructure capability.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9