agentleFS
Sign inStart free
NikoxkxNikoxkx/Agent-Skills/skills/devops/backup-strategy/SKILL.md

backup-strategy

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Designs and implements a backup and disaster recovery strategy for databases and file storage. Use when setting up backups for production data.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Delete a file or row in prod and confirm it can be recovered from backup.

    line 81
  2. Distinctive:

    Check that old backups are being expired per policy.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Designs a complete backup and disaster recovery (DR) strategy including RPO/RTO definitions, backup methods for databases (pg_dump, WAL archiving, snapshots), file/object storage backups, S3 lifecycle rules, encryption at rest and in transit, automated restore testing, retention schedules following the 3-2-1 rule, and an incident runbook template for restore scenarios.

When to Use This Skill

  • Setting up production data protection for the first time.
  • Auditing or improving existing backup processes.
  • Preparing for compliance or business continuity requirements.

Prerequisites

  • Production databases and file storage identified.
  • Access to S3 or equivalent object storage with versioning/lifecycle.
  • Ability to run backup jobs (cron, Kubernetes CronJob, cloud scheduled tasks).

Steps

  1. Define RPO and RTO for each data tier:
    • RPO (Recovery Point Objective): How much data loss is acceptable?
    • RTO (Recovery Time Objective): How long to restore service?
  2. Database backup methods (choose per DB):
    • Full logical (pg_dump, mysqldump) — good for small DBs or point-in-time restore needs.
    • Continuous WAL / PITR (PostgreSQL pg_basebackup + archiving, MySQL binlog).
    • Storage snapshots (EBS, GCP PD, Azure Disk) — fast for large DBs.
    • Managed service backups (RDS automated, Cloud SQL, etc.).
  3. File / object storage:
    • S3 versioning + cross-region replication.
    • Lifecycle policies: transition to IA/Glacier after 30/90 days, expire after retention period.
  4. Encryption & security:
    • Encrypt backups at rest (KMS or S3 SSE).
    • Encrypt in transit (TLS).
    • Least-privilege IAM for backup jobs.
  5. Retention (3-2-1 rule):
    • 3 copies of data.
    • 2 different media/types.
    • 1 offsite / in different region/account.
  6. Automated restore testing:
    • Schedule monthly/quarterly restore to a staging environment.
    • Script the restore and verify data integrity (row counts, checksums).
    • Document the runbook.
  7. Output:
    • Backup architecture diagram (text or Mermaid).
    • Cron / CronJob / cloud schedule definitions.
    • Restore scripts (example for Postgres from S3).
    • Retention policy.
    • Incident runbook template for "data loss event".

Examples

A complete strategy for a PostgreSQL + S3 user uploads system is included, with pg_dump + WAL shipping to S3, lifecycle rules, a restore script, and a quarterly restore test CronJob.

Edge Cases & Error Handling

  • Partial corruption: PITR allows restoring to just before the corruption.
  • Ransomware / malicious delete: Immutable backups (S3 Object Lock, WORM) or cross-account backups.
  • Cost control: Lifecycle policies + infrequent access / Glacier.

Verification

  1. Backups are running on schedule and landing in the correct location.
  2. A test restore completes within the target RTO and data is verified correct.
  3. Delete a file or row in prod and confirm it can be recovered from backup.
  4. Check that old backups are being expired per policy.
  5. Success: RPO and RTO targets are met, restores are tested regularly, and data is protected against common failure modes including human error and ransomware.

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free